|
||||||||
|
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.
Code changed in jenkins
User: Steven Brown
Path:
src/main/java/org/jfrog/hudson/ArtifactoryRedeployPublisher.java
src/main/java/org/jfrog/hudson/maven3/extractor/MavenExtractorHelper.java
http://jenkins-ci.org/commit/artifactory-plugin/7b33abcac3b3704eb6c15f6bddbadf92cd1169f5
Log:
HAP-373 - For multi-module M2 release builds, don't publish artifacts
When releasing a single Maven module with the M2 Release plugin, the
ArtifactoryRedeployPublisher does not publish any artifacts. This was
implemented under HAP-93.
This change makes multi-module Maven builds act the same way. The
artifactory plugin will act as if there is no ArtifactoryRedeployPublisher
configured when performing a M2 Release, and so will not deploy artifacts.
See also JENKINS-16780, which appears to describe the same bug.