versions: Regression in 2.14.0
git clone https://github.com/vaadin/flow.git
cd flow
mvn versions:set -DnewVersion=1.2.3
Expected outcome: All modules are set to version 1.2.3, like with 2.13.0
Actual outcome:
[ERROR]
java.nio.file.NoSuchFileException: /.../flow/flow-tests/test-npm-only-features/test-npm-bytecode-scanning/pom.xml
at sun.nio.fs.UnixException.translateToIOException (UnixException.java:92)
at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:106)
at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:111)
at sun.nio.fs.UnixFileSystemProvider.newByteChannel (UnixFileSystemProvider.java:219)
at java.nio.file.Files.newByteChannel (Files.java:380)
at java.nio.file.Files.newByteChannel (Files.java:432)
at java.nio.file.spi.FileSystemProvider.newInputStream (FileSystemProvider.java:422)
at java.nio.file.Files.newInputStream (Files.java:160)
at org.codehaus.plexus.util.xml.XmlReader.<init> (XmlReader.java:129)
at org.codehaus.plexus.util.xml.XmlStreamReader.<init> (XmlStreamReader.java:67)
at org.codehaus.plexus.util.ReaderFactory.newXmlReader (ReaderFactory.java:122)
at org.codehaus.mojo.versions.api.PomHelper.readXmlFile (PomHelper.java:1498)
at org.codehaus.mojo.versions.AbstractVersionsUpdaterMojo.process (AbstractVersionsUpdaterMojo.java:326)
at org.codehaus.mojo.versions.SetMojo.execute (SetMojo.java:381)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
and the version in the following modules is not updated:
flow-tests/test-ccdm-flow-navigation/pom-production.xml
flow-tests/test-ccdm/pom-production.xml
flow-tests/test-custom-frontend-directory/test-themes-custom-frontend-directory/pom-generatedTsDir.xml
flow-tests/test-frontend/test-npm/pom-production.xml
flow-tests/test-frontend/test-pnpm/pom-production.xml
flow-tests/test-frontend/vite-context-path/pom-production.xml
flow-tests/test-frontend/vite-embedded/pom-production.xml
flow-tests/test-frontend/vite-pwa-custom-offline-path/pom-production.xml
flow-tests/test-frontend/vite-pwa-disabled-offline/pom-production.xml
flow-tests/test-npm-only-features/test-npm-bytecode-scanning/pom-devmode.xml
flow-tests/test-npm-only-features/test-npm-bytecode-scanning/pom-prod-fallback.xml
flow-tests/test-npm-only-features/test-npm-bytecode-scanning/pom-production.xml
flow-tests/test-pwa-disabled-offline/pom-production.xml
flow-tests/test-pwa/pom-production.xml
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 12
- Comments: 37 (17 by maintainers)
Commits related to this issue
- Resolves #848: Fixing module resolution with nonstandard filenames — committed to ajarmoniuk/versions-maven-plugin by ajarmoniuk 2 years ago
- Specify versions-maven-plugin version explicitly If version not specified explicitly maven-cli downloads the latest Regression have been introduced in version 2.14.0 https://github.com/mojohaus/versi... — committed to JetBrains/kotlin by Badya 2 years ago
- Specify versions-maven-plugin version explicitly If version not specified explicitly maven-cli downloads the latest Regression have been introduced in version 2.14.0 https://github.com/mojohaus/versi... — committed to JetBrains/kotlin by Badya 2 years ago
- Resolves #848: Fixing module resolution with nonstandard filenames — committed to ajarmoniuk/versions-maven-plugin by ajarmoniuk 2 years ago
- Resolves #848: Fixing module resolution with nonstandard filenames — committed to ajarmoniuk/versions-maven-plugin by ajarmoniuk 2 years ago
- Resolves #848: Fixing module resolution with nonstandard filenames — committed to ajarmoniuk/versions-maven-plugin by ajarmoniuk 2 years ago
- Resolves #848: Fixing module resolution with nonstandard filenames — committed to ajarmoniuk/versions-maven-plugin by ajarmoniuk 2 years ago
- Pin versions-maven-plugin version to 2.13.0. 2.14.0 has a bug (https://github.com/mojohaus/versions/issues/848) that broke us. We should be pinning all build tool versions, anyway. — committed to aws/aws-sdk-java-v2 by millems 2 years ago
- Pin versions-maven-plugin version to 2.13.0. (#3623) 2.14.0 has a bug (https://github.com/mojohaus/versions/issues/848) that broke us. We should be pinning all build tool versions, anyway. — committed to aws/aws-sdk-java-v2 by millems 2 years ago
- IMPALA-11800: Pin versions:set to 2.13.0 to avoid regression Pins the versions maven plugin to 2.13.0 to avoid https://github.com/mojohaus/versions/issues/848, which causes our all-build-options run ... — committed to apache/impala by MikaelSmith 2 years ago
- HIVE-26849: Nightly build fails in master from build 1533 onwards (Stamatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (https://... — committed to apache/hive by zabetak 2 years ago
- HIVE-26849: Nightly build fails in master from build 1533 onwards (Stamatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (https://... — committed to dengzhhu653/hive by zabetak 2 years ago
- GH-14949: [CI][Release] Output script's stdout on failure (#14957) This doesn't solve GH-14949 (CI failure) because it's a problem of MojoHaus Versions Maven Plugin: https://github.com/mojohaus/vers... — committed to apache/arrow by kou 2 years ago
- HIVE-26849: Nightly build fails in master from build 1533 onwards (Stamatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (https://... — committed to tarak271/hive-1 by zabetak 2 years ago
- HIVE-26849: Nightly build fails in master from build 1533 onwards (Stamatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (https://... — committed to DongWei-4/hive by zabetak 2 years ago
- HIVE-26849: Nightly build fails in master from build 1533 onwards (Stamatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (https://... — committed to rkirtir/hive by zabetak 2 years ago
- HIVE-26849: Nightly build fails in master from build 1533 onwards (Stamatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (https://... — committed to yeahyung/hive by zabetak 2 years ago
- HIVE-26849: Nightly build fails in master from build 1533 onwards (Stamatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (https://... — committed to tarak271/hive-1 by zabetak 2 years ago
Fix merged.
Please someone more to also check.
I can release 2.14.1 tomorrow 😄
⚠️ Version
2.14.1released - please retest@pzygielo could you please share some details about your case? Alternatively, could you try your test case against my branch? Thanks
The old assumption about the “pom.xml” file in module directories dates back to the very beginning of the Set mojo. I wonder how (if) it worked in 2.13.0 (the mojo simply skipped files it couldn’t resolve). Anyway, the original case as well a simplified case (it-set-issue-848) do work fine with the branch.
And the solution is simple – since we already have the path, why not use it? 😃
Everyone – until this is released, please use
to get around the problem. Sorry about the inconvenience.
Same issue here! Thanks for acting quick!
I see that not everybody is constraining the plugin version, already 3 Apache projects suffering from the bug.
I hope we will have a fix soon 😄
2.15.0-SNAPSHOT - built from 60cda6ac, works fine 🎉
Here it is extracted to minimum:
with top-level having
and module with
Possible workarounds:
<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>versions-maven-plugin</artifactId> <version>2.13.0</version> </plugin>OR
@joviegas when you execute a Maven command, Maven outputs which plugins it has executed and which modules (POM files) it has processed. In your example, Maven itself (not the plugin) had a problem processing the input files - it could not retrieve the parent file of one of the POM files. In any case, it’s not an issue with this plugin.
@slawekjaranowski it’s not an issue with the plugin – it’s not even been executed.
Our project hits the issue since yesterday, now it works flawlessly. Thanks for the quick fix!
I re ran my original test mentioned above using
and it now produces identical results with 2.13 🎉
Yes - I think it’s common to run, e.g.,
man versions:setfor ad-hoc tasks; this means that in the absence of any POM configuration latest is pulled.I observe similar - version is not set in modules with parent not in
..<parent>... <relativePath>../..</relativePath>Gotcha. Sorry about that. I’ll look into it.