-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in 2.14.0 #848
Comments
Gotcha. Sorry about that. I'll look into it. |
I observe similar - version is not set in modules with parent not in
|
Sorry to hijack this issue, but perhaps it's related. |
I suppose it has something to do with the assumptions versions/versions-common/src/main/java/org/codehaus/mojo/versions/api/PomHelper.java Line 1219 in efec55e
versions/versions-common/src/main/java/org/codehaus/mojo/versions/api/PomHelper.java Line 1302 in efec55e
that pom.xml is the right file name...
|
I have the same problem when I do mvn versions:set, please keep us informed java.nio.file.NoSuchFileException: /home/jenkins/agent/workspace/curve-connector-test_release_0.2/dtos |
Also have this issue |
Possible workarounds:
OR
|
it works for me! thanks. I didn't have to add it in the parent pom |
@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 mvn org.codehaus.mojo:versions-maven-plugin:2.13.0 to get around the problem. Sorry about the inconvenience. |
2.15.0-SNAPSHOT - built from 60cda6a, works fine 🎉
Here it is extracted to minimum:
with top-level having <modules>
<module>docs/issue</module>
</modules> and module with <parent>
...
<relativePath>../..</relativePath>
</parent> |
If version not specified explicitly maven-cli downloads the latest Regression have been introduced in version 2.14.0 mojohaus/versions#848
If version not specified explicitly maven-cli downloads the latest Regression have been introduced in version 2.14.0 mojohaus/versions#848 (cherry picked from commit 9c1a68f)
This is exactly what happens. When there is an intermediate parent directory without pom.xml, it fails to version bump that. It starts looking for that module in root of the project. |
we have the same issue right now plaguing all of our maven builds because |
@ahannani-rms as a workaround, please use
|
Is it possible to remove |
Or push 2.14.1 with 2.13.0 content? |
It is not possible: https://central.sonatype.org/faq/can-i-change-a-component/ By the way is good practice to specific plugins versions in project. |
I hope we will have a fix soon 😄 |
2.14.0 has a bug (mojohaus/versions#848) that broke us. We should be pinning all build tool versions, anyway.
Yes - I think it's common to run, e.g., |
Also have this issue |
Same issue here! Thanks for acting quick! |
Thanks for responding quickly with a fix. really appreciate it. |
|
I re ran my original test mentioned above using
and it now produces identical results with 2.13 🎉 |
Can confirm this fixes the regression for me. |
👍 |
…amatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (mojohaus/versions#848) causing the failures in the nightly build. Using a fixed version is a good practice and can also prevent similar problems in the future. Closes apache#3860
|
Yes I noticed the same, assumed it was just delayed propagation or something |
Updating of local stored artifact is done once per day in standard way - In order to pressure update use |
Our project hits the issue since yesterday, now it works flawlessly. Thanks for the quick fix! |
This doesn't solve GH-14949 (CI failure) because it's a problem of MojoHaus Versions Maven Plugin: mojohaus/versions#848 This adds more debug information on test failure. * Closes: #14949 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…amatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (mojohaus/versions#848) causing the failures in the nightly build. Using a fixed version is a good practice and can also prevent similar problems in the future. Closes apache#3860
is failing with 2.14.1 This used to pass with 2.13.0 and also 2.14.0
Also strange thing is this passes when the build is re-tried , it happens only first time |
@joviegas please create new issue - with simple project which allow us to reproduce. |
@slawekjaranowski it's not an issue with the plugin -- it's not even been executed. |
@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. |
I pinned the maven plugin version to 2.13.0 and this fixed the issue , without any changes in our code/pom.
Note earlier it was picking the latest one that was 2.14.1 , and we started seeing this issue only for this version. |
…amatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (mojohaus/versions#848) causing the failures in the nightly build. Using a fixed version is a good practice and can also prevent similar problems in the future. Closes apache#3860 (cherry picked from commit 2cf058b)
…amatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (mojohaus/versions#848) causing the failures in the nightly build. Using a fixed version is a good practice and can also prevent similar problems in the future. Closes apache#3860
…amatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (mojohaus/versions#848) causing the failures in the nightly build. Using a fixed version is a good practice and can also prevent similar problems in the future. Closes apache#3860
…amatis Zampetakis reviewed by Laszlo Bodor) Freeze versions-maven-plugin to 2.13.0 to overcome the regression of 2.14.0 (mojohaus/versions#848) causing the failures in the nightly build. Using a fixed version is a good practice and can also prevent similar problems in the future. Closes apache#3860
Expected outcome:
All modules are set to version 1.2.3, like with 2.13.0
Actual outcome:
and the version in the following modules is not updated:
The text was updated successfully, but these errors were encountered: