You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if it's intentional when calling update-properties to check the metadata of all defined dependencies if we pass includesList which will end up skipping version updates for most of them?
I invoke something like this: mvn org.codehaus.mojo:versions-maven-plugin:2.16.2:update-properties -DallowMinorUpdates=false -Dincludes=my.groupId.*,my.other.groupId.*
And for some projects it takes even about 30 minutes to finally update only a few of my own dependencies among the multitude of third-party dependencies that I do not want to update automatically.
The text was updated successfully, but these errors were encountered:
I wonder if it's intentional when calling update-properties to check the metadata of all defined dependencies if we pass includesList which will end up skipping version updates for most of them?
I invoke something like this:
mvn org.codehaus.mojo:versions-maven-plugin:2.16.2:update-properties -DallowMinorUpdates=false -Dincludes=my.groupId.*,my.other.groupId.*
And for some projects it takes even about 30 minutes to finally update only a few of my own dependencies among the multitude of third-party dependencies that I do not want to update automatically.
The text was updated successfully, but these errors were encountered: