-
Bug
-
Resolution: Unresolved
-
Major
-
None
I want to set up maven installs by auto-installing the stock apache release and then applying a company-specific global settings file. The job configuration requires the pathname to a global settings to be workspace-relative. Why? If I've carefully arranged for a pathname to be available everywhere, or relative to the jenkins home dir, why not.
Better yet, please consider allowing a global settings file to accompany the definition of a maven installer.
[JENKINS-10087] Frustrating limitation on maven global settings location
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: maven2 [ 15487 ] |
Workflow | Original: JNJira [ 140275 ] | New: JNJira + In-Review [ 175239 ] |