Gradle plugin appears to cause artifacts to end up in maven local cache

[davidmc24]

I'm using the Gradle plugin by way of the Artifactory Bamboo plugin. In the configuration of the Artifactory Gradle task, I specify to call the "build" task, "Capture and Publish Build Info", "Publish Artifacts to Artifactory", "Publish Maven Descriptors", and "Use Maven 2 Compatible Patterns".

In my Bamboo logs, I see that the "artifactoryPublish" task is preceded by the "install" due to a dependency. Having "install" called results in the artifacts ending up in the maven local cache on the CI server, causing unnecessary disk usage and need for cleanup.

I think that the problematic logic may be around here:

https://github.com/JFrogDev/build-info/blob/a78049b65043e9eca2d5bbd20a3d12164521a033/build-info-extractor-gradle/src/main/groovy/org/jfrog/gradle/plugin/artifactory/task/BuildInfoConfigurationsTask.java#L374