|
||||||||
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 |
- [JIRA] (JENKINS-14637) Maven Deployment Linker do... ra...@kubacki.cz (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... lshat...@java.net (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... lshat...@java.net (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... ra...@kubacki.cz (JIRA)
- [JIRA] (JENKINS-14637) Maven Deployment Link... lshat...@java.net (JIRA)
The name "linker" in the plugin name does not mean permlinks, but hyperlinks that it puts in the job page. The m2 release plugin already puts a link to the build that caused the release. It seems like a bug for the m2 release plugin, since this plugin is only to put hyperlinks on the build/job pages. It does this by scanning the log of the build for all artifacts uploaded to a maven repository by means of a regex.
Also some maven jobs (usually multi-module ones) produce multiple artifacts, so how would it know which one(s) to put in the permalink, if there was one?