[x] All tests passed. If this feature is not already covered by the tests, I added new
tests.
Currently, the deployable artifacts mechanism adds the deployable artifacts only if the artifacts are deployed. However, there's a requirement for these deployable artifacts even when they haven't been deployed yet, so we can deploy them at a later time. For instance, the command jf gradle clean aP --scan is used to analyze the deployable artifacts and then deploy the ones that are non-vulnerable.
Currently, the deployable artifacts mechanism adds the deployable artifacts only if the artifacts are deployed. However, there's a requirement for these deployable artifacts even when they haven't been deployed yet, so we can deploy them at a later time. For instance, the command
jf gradle clean aP --scanis used to analyze the deployable artifacts and then deploy the ones that are non-vulnerable.This PR make it work like v4 of this plugin: https://github.com/jfrog/build-info/blob/build-info-gradle-extractor-4.33.4/build-info-extractor-gradle/src/main/groovy/org/jfrog/gradle/plugin/artifactory/task/DeployTask.java#L193