|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I investigates this some, and the behavior is as follows:
The global configuration only changes the default setting of newly created 'Top-level Maven targets' build steps. So if you specify a path in the global configuration, that's explicitly the default setting for new maven build steps. "Use default Maven settings" in this context actually means "use the Maven default", and not "Use whatever is configured in the global configuration as the default [for new build steps]".
This seems to behave as designed, so I'm resolving this as Not a Defect.