-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 1.539
Both Linux and Windows versions affected.
Changing the default setting provider under /configure -> Maven Configuration has no effect. No matter what either the local or global setting provider is set to, Maven always uses the defaults, i.e. the setting files of the user and the Maven installation.
Executing Maven: -B -f w:\Devenv\Jenkins\config-file-provider-plugin\work\jobs\test_maven\workspace\pom.xml help:effective-settings