-
Notifications
You must be signed in to change notification settings - Fork 267
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
versions:lock-snapshots after upgrading from 2.13.0 to 2.14.0 #899
Comments
@g-chcht could you provide a pom.xml which contains a snapshot to lock so that we could try to reproduce the issue? |
Never mind, managed to reproduce it with a bespoke pom. And confirmed. Thanks for the report. |
@g-chcht to be on the safe side, could you please provide an artifact which you wanted to lock so that we could verify the fix using real world artifacts? |
@slawekjaranowski unfortunately, hard to fix with the use of mrm-maven-plugin: no metadata found even with 2.13.0 (before the switch to Resolver). Do you happen to know any timestamped maven artifacts to test it against? Edit: found one. |
…ve the timestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
…ve the timestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
…ve the timestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
…ve the timestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
…ve the timestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
…ve the timestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
…ve the timestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
Hey, |
Nope. Again, thanks for the report. |
…imestamped snapshot version; added unit tests for LockSnapshotsMojo for the case when no timestamped versions are found
Hello guys,
Full name:
org.codehaus.mojo:versions-maven-plugin:2.14.0:lock-snapshots
What steps will reproduce the bug?
mvn -U --batch-mode org.codehaus.mojo:versions-maven-plugin:2.14.0:lock-snapshots
What is the expected behavior?
What do you see instead?
-SNAPSHOT
not replaced in pom.xmlAdditional information
Regards,
The text was updated successfully, but these errors were encountered: