My bad, it is indeed the Ubuntu that is failing.
It might be caused be JDK-8177809[1]
IIRC when using Path instead of File you won't have this issue.
Robert
[1] https://bugs.openjdk.java.net/browse/JDK-8177809
On 27-7-2020 07:31:41, Christian Stein wrote:
Hi,
Why do you think it's the Windows
Hi,
Why do you think it's the Windows node, Robert?
For me, it [1] says 5 times: linux-jdk8-m3.6.x_build
The file separator chars displayed in the log file also points to a Linux
node:
>
> [INFO] The post-build script did not succeed. assert buildLog.text =~
> /(?i) Archive .*${sourcesJarFileN
elharo merged pull request #184:
URL: https://github.com/apache/maven-site/pull/184
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
edburns commented on pull request #184:
URL: https://github.com/apache/maven-site/pull/184#issuecomment-664035432
@mkarg @elharo Squashed into 79d956f6a .
This is an automated message from the Apache Git Service.
To respond
edburns commented on pull request #184:
URL: https://github.com/apache/maven-site/pull/184#issuecomment-664033736
I can certainly squash, no problem at all.
This is an automated message from the Apache Git Service.
To res
Anybody willing to analyze why this plugin is broken for a while?[1]
It look like there hasn't been a commit since the last success (recent changes
only show commits on our Jenkins files)
All other master are currently stable.[2]
thanks,
Robert
[1] https://builds.apache.org/job/maven-box/job/ma
