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'm attempting to use findbugs and pmd in my buildscript, eg:
apply plugin: 'pmd'
apply plugin: 'findbugs'
According to the documentation (findbugs | pmd) these two plugins add additional dependency configurations, 'findbugs' and 'pmd'.
Adding these to my offlineDependencies { configurations } doesn't result in an error, but it looks like the dependencies are determined at the runtime of the plugin, and as such aren't available when running ./gradlew updateOfflineRepository
I was able to work around this by running ./gradlew check updateOfflineRepository which causes the dependency configurations for these tools to be resolved and the offline repository populated with the needed dependencies.
I imagine this could be an issue with a number of the default gradle plugins. While this is an ok workaround, I wonder if there's any way to find and force evaluation of plugin provided dependency configurations?
The text was updated successfully, but these errors were encountered:
I'm attempting to use findbugs and pmd in my buildscript, eg:
According to the documentation (findbugs | pmd) these two plugins add additional dependency configurations, 'findbugs' and 'pmd'.
Adding these to my offlineDependencies { configurations } doesn't result in an error, but it looks like the dependencies are determined at the runtime of the plugin, and as such aren't available when running
./gradlew updateOfflineRepository
I was able to work around this by running
./gradlew check updateOfflineRepository
which causes the dependency configurations for these tools to be resolved and the offline repository populated with the needed dependencies.I imagine this could be an issue with a number of the default gradle plugins. While this is an ok workaround, I wonder if there's any way to find and force evaluation of plugin provided dependency configurations?
The text was updated successfully, but these errors were encountered: