Add a JF_PLUGINS_REPO to complement JF_DEPS_REPO for Maven builds

[jghal]

Is your feature request related to a problem? Please describe. We configure Artifactory and Maven to use different Maven repositories for plugins and dependencies. Running Frogbot this way is failing because it's ignoring Maven settings files and subsequently can't load the plugins.

Describe the solution you'd like to see I would like to see Frogbot just use the already-correct Maven configuration directly instead of have to perform redundant configuration that developers will lose a day to when they forget they have to change Frogbot configuration every time they change the Maven configuration. There is no implementation of frogbot that would make developer adoption easier and faster than just directly supporting the Maven configuration. But barring that I would like to see a JF_PLUGINS_REPO env variable so that we can maintain our separation of plugins vs dependencies.

Describe alternatives you've considered After talking with JFrog support it seems our only option is to combine our plugins and dependencies Maven repos with virtual repos in Artifactory and configure JF_DEPS_REPO with that combined repo.

[eyalbe4]

Thanks for sharing this requirement with us @jghal. Where is the settings.xml file used by the developers stored? Is it included as part of the source code in git?

[jghal]

We store credentials and a file template in CI (Jenkins credentials and config file provider plugin, GitLab CI/CD variables) and then create the file within in our pipeline, then there can also be files in .mvn directory committed to source code.