Description
Is your feature request related to a problem? Please describe.
Currently, If we use 'jf gradle-config', it doesn't support the notion of a snapshot repository and doesn't appear to support any sort of configuration with Gradle'smaven-publish plugin. This makes it difficult/not possible to use 'jf gradle' with Maven repositories (which is a very common use case across Enterprise).
As an example, the configuration for 'jf gradle' :
❯ jf gradlec Password: Resolve dependencies from Artifactory? (y/n) [y]? y Set Artifactory server ID [hts]: hts Set repository for dependencies resolution maven-virtual Deploy project artifacts to Artifactory? (y/n) [y]? y Set Artifactory server ID [hts]: hts Set repository for artifacts deployment maven-local Deploy Maven descriptors? (y/n) [n]? y Deploy Ivy descriptors? (y/n) [n]? n Is the Gradle Artifactory Plugin already applied in the build script? (y/n) [n]? n Use Gradle wrapper? (y/n) [y]? y 10:27:46 [🔵Info] gradle build config successfully created.
As seen above (no mention of snapshot logic mentioned in configuration)
On the contrary, for jf mvnc:
❯ jf mvnc Resolve dependencies from Artifactory? (y/n) [y]? y Set Artifactory server ID [hts]: hts Set resolution repository for release dependencies maven-virtual Set resolution repository for snapshot dependencies libs-snapshot Deploy project artifacts to Artifactory? (y/n) [y]? y Set Artifactory server ID [hts]: hts Set repository for release artifacts deployment maven-local Set repository for snapshot artifacts deployment libs-snapshot Would you like to filter out some of the deployed artifacts? (y/n) [n]? n Use Maven wrapper? (y/n) [y]? y 10:32:05 [🔵Info] maven build config successfully created.
Describe the solution you'd like to see
The ask is, to enable 'jf gradle' to work in the similar fashion to 'jf mvn' where jf gradle can be used cross compatibly with maven repositories as well. This is a common use case in enterprise and should be integrated as such to JFrog CLI.
Describe alternatives you've considered
Alternatively, without JFrog CLI, if using plain Maven and Gradle client, certain configuration blocks could be added to support the use-case, which many customers have been doing. However, since CLI generates its own config, this has become difficult from a customer standpoint.