[JIRA] [core] (JENKINS-26618) "Use private Maven repository" within "Invoke top-level Maven targets" issues.

[dan...@beckweb.net (JIRA)]

Daniel Beck commented on JENKINS-26618 "Use private Maven repository" within "Invoke top-level Maven targets" issues. Cannot reproduce issue #1. Please try to reproduce this on a new Jenkins home directory with the current release of Jenkins (1.598), e.g. export JENKINS_HOME=$HOME/JENKINS-26618-Test ; java -jar jenkins.war --httpPort=8787 Please also provide complete steps to reproduce the issue. Obviously, "Select invoke top-level maven targets" is missing, but is there anything else missing as well? When disabling "Use private Maven repository" option for "Invoke top-level Maven target" build step, it does not honor the global setting. Issue #2 likely stems from the fact that 'Invoke top-level Maven targets' is a core-provided build step, while the Maven Project type and its configuration are provided by the optional, installed-by-default (for backwards compatibility reasons) Maven Integration plugin. If so (disable the Maven Integration plugin and see whether the global config section vanishes), not a real bug, just user confusion caused feature overlap between independent components.

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.