Ignore specific dependencies #867
Replies: 2 comments 1 reply
-
It’s not the prettiest, but the most flexible approach is to use a custom report format to modify the results before printing them using our built-in ones. Here is an example when I did this while a dependency had bad metadata on central. I moved it into the correct section until they got Sonatype’s help and fixed that. You could easily remove or otherwise adjust similarly. |
Beta Was this translation helpful? Give feedback.
-
I'm fine with the workaround as well. I thought maybe we could create a convenience method to make it easier. Or even automatically determine that certain dependency reports are unnecessary. However, I currently don't see how that could work. Even though I have built one or two Gradle plugins, I'm not familiar with the details in the area of configurations 🙈. |
Beta Was this translation helpful? Give feedback.
-
In some situations, dependency updates are irrelevant. For example, when developing a Gradle plugin and using the
kotlin-dsl
plugin, because the internal Gradle Kotlin version is used in that case.Currently, however, all Kotlin updates are reported, even though you cannot change the version.
You can solve this with
rejectVersionIf
, for example, with the following condition:I don't know if it's possible to automatically determine that the internal Kotlin version should be used, but a filter could simplify this:
Unfortunately,
checkConstraints
andcheckBuildEnvironmentConstraints
do not help here either.Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions