[JIRA] (JENKINS-14653) Copy Artifacts plugin does not accept Maven module as Project Name.

[ranki...@yahoo.com (JIRA)]

Chris Rankin created JENKINS-14653 Copy Artifacts plugin does not accept Maven module as Project Name. Issue Type: Bug Affects Versions: current Assignee: Alan Harder Components: copyartifact Created: 01/Aug/12 1:53 PM Description: When copying artifacts from a Maven project: if you type the bare Jenkins project name (i.e. "my-build-trunk") into the "Project Name" field then Jenkins will display the message: "Artifacts will be copied from all modules of this Maven project; click the help icon to learn about selecting a particular module." At this point, a reasonable user would expect to be able to configure a Maven module instead, e.g. "my-build-trunk/com.stuff.my$moduleName". However, the TriggeredBuildSelector does not understand Maven project names because it is only expecting a bare Jenkins project name. This creates such frustration and confusion that users are forced to examine the plugin's source code to find out WHAT ON EARTH is going wrong. Environment: Windows 7, Project: Jenkins Priority: Major Reporter: Chris Rankin

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