-
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:use-latest-versions doesn't set previous releases when allowSnapshot=false #213
Comments
Thanks @DiJu519 - I see |
Last time i was in the code I did not see it implemented. |
Hopefully it's not too much effort to use the same strategy for some of the other goals. |
@jdileonardo I think this one is still an issue - I don't see the |
Looking into it. |
…f allowSnapshots is false, will optionally downgrade the dependency version if its current version is a snapshot
…f allowSnapshots is false, will optionally downgrade the dependency version if its current version is a snapshot
…f allowSnapshots is false, will optionally downgrade the dependency version if its current version is a snapshot
…f allowSnapshots is false, will optionally downgrade the dependency version if its current version is a snapshot
…f allowSnapshots is false, will optionally downgrade the dependency version if its current version is a snapshot
…f allowSnapshots is false, will optionally downgrade the dependency version if its current version is a snapshot
…napshots is false, will optionally downgrade the dependency version if its current version is a snapshot
I have a use-case where I use-latest-versions where I allowSnapshots on my mainline (which works great) but when I set it to try to swap all the snapshots to releases for my release branch using
-DallowSnapshots=false
, it won't "go back in versions" to use the latest release version.Example:
pom.xml
has1.1-20170929132713
but I want to have it update to the latest release candidate which is1.0
Is there a way to get this behavior or is it a new feature?
The text was updated successfully, but these errors were encountered: