-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins Artifactory Plugin version: 2.13.1
CloudBees Jenkins Enterprise 2.89.1.6-rolling
While we were updating our Maven installation from version 3.3.9 to version 3.5.2, we found that Jenkins failed to read our global settings.xml file which defined our Maven Central mirrors.
Digging into the issue, I found that this commit introduced a new system property maven.conf that maven uses to detect the global configuration settings file. As a backport solution, they added this line to the global $(maven.home)/bin/m2.conf file:
set maven.conf default ${maven.home}/conf
Since the Artifactory plugin does not process the $(maven.home)/bin/m2.conf file, this default setting is never configured, thus Artifactory can't find the global settings file.
I validated this issue by passing -Dmaven.conf=/opt/maven/default/conf (where we have our maven installation) to the goals parameter on the rtMaven.run function.
I'd like to see Artifactory define the maven.conf variable like it does with maven.home.