Replies: 1 comment 2 replies
-
Unfortunately rejecting all of the versions forces each prior to be evaluated, which Gradle does sequentially. So it is slow as you noticed and results in a resolution error in the logs. In #453, the solution snippets use a resolution rule to force the version. This way the dynamic query ( Another approach is to exclude them by using a custom report, where an outputFormatter {
def reporter = new PlainTextReporter(project, revision, gradleReleaseChannel)
outdated.dependencies.removeIf { isManagedBySpringBoot(it) }
reporter.write(System.out, this)
} Otherwise, right now we don't have a |
Beta Was this translation helpful? Give feedback.
-
Hi,
I think I have a way of excluding spring-boot dependencies from the result of
dependencyUpdates
but I think there may be a simpler or more elegant way of doing it. I used the example of exluding isNonStable as in the examples and it seems to work.Here is my way of excluding in the
But. I'm not sure about the inner workings of gradle and the plugin and it looks that when a version is rejected it tries another version and therefor download xml poms with the next lower version so the dependencyUpdates takes much more time and many more downloads.
So my question here is if there is a more elegant way of doing this.
This is the some of the result and it seems good, but I also tried the more verbose way of sending a reason with the rejection and it would be nice to get that also:
Regards Per Jonsson
Beta Was this translation helpful? Give feedback.
All reactions