One is forced to call ./gradlew publishToMavenLocal in order ./gradlew [auto|lintGradle] to pass
geirsandearm opened this issue · 1 comments
geirsandearm commented
When module uses following gradle plugins
apply plugin: "com.github.johnrengelman.shadow"
apply plugin: "maven-publish"
apply plugin: "java-library"
developer needs to call ./gradlew publishToMavenLocal
in order to linting to pass. Otherwise when linting it isn't able to load pom for that particular module e.g.
`
:lintGradle > Resolve dependencies of :myproject:detachedConfiguration4 > myproject-0.1-fbcb30721d.pom
`
Is there anyway possible to skip/exclude this kind of linting?
geirsandearm commented
When I applied
apply plugin: "nebula.resolution-rules"
problem went away.