Closed imagejan closed 1 year ago
I was wrong: current master
does build on Windows, but it starts failing when you bump the parent pom-scijava
version to 23.1.1
.
Update: pinning to <maven-surefire-plugin.version>2.19.1</maven-surefire-plugin.version>
fixes the build on Windows with pom-scijava 23.1.1
.
Something must have changed in maven-surefire-plugin between 2.19 and 2.21.
Update2: the breaking change is between versions 2.20
(passing) and 2.20.1
(failing) of maven-surefire-plugin
.
@imagejan Could you try with maven-surefire-plugin 2.22.0? If it works, we can update pom-scijava-base accordingly. If it doesn't work, we could revert to the most recent older working version.
Could you try with maven-surefire-plugin 2.22.0?
The test keeps failing with <maven-surefire-plugin.version>2.22.0</maven-surefire-plugin.version>
.
same issue as https://github.com/imagej/imagej-legacy/issues/234
Update: I tested pinning to <maven-surefire-plugin.version>3.0.0-M4</maven-surefire-plugin.version>
and MacroTest passed again.
I suggest we bump the version of maven-surefire-plugin
in pom-scijava-base
to 3.0.0-M4 here: https://github.com/scijava/pom-scijava-base/blob/e503582fb3e19ced75e12487322f70ddcb3cfde5/pom.xml#L236
I couldn't access the changelogs here, but we should probably see rather quickly with the melting-pot
script if anything breaks.
When building with
mvn clean install
on Windows (Git Bash),MacroTest#testBarePluginFromMacro()
fails with:The issue seems to be Windows-specific, as builds on Travis run fine.