-
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
Version updates ignore import scoped BOM dependencies #25
Comments
tavin
added a commit
to tavin/versions-maven-plugin
that referenced
this issue
Feb 8, 2016
tavin
added a commit
to tavin/versions-maven-plugin
that referenced
this issue
Feb 9, 2016
see pull request above -- we've been using my patch for 3+ months with no problems |
khmarbaise
added a commit
that referenced
this issue
Jun 12, 2016
fix #25 use raw model for dependencyManagement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version 2.2
As per http://stackoverflow.com/questions/7609876/how-to-make-maven-versionsuse-latest-versions-step-up-import-scoped-entry-in-de
When we run mvn versions:use-latest-versions all our dependencies (and other entries in dependencyManagement) get stepped up except this one.
The text was updated successfully, but these errors were encountered: