chibbe created MNG-5939:
---------------------------
Summary: Problem doing release when sources are generate as well
Key: MNG-5939
URL: https://issues.apache.org/jira/browse/MNG-5939
Project: Maven
Issue Type: Bug
Affects Versions: 3.3.9
Environment: Ubuntu 12.04.5 LTS
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T18:37:52+01:00)
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Java version: 1.7.0_76, vendor: Oracle Corporation
Reporter: chibbe
If I specified that sources should be generated with jar-no-fork goal
https://maven.apache.org/plugins/maven-source-plugin/jar-no-fork-mojo.html .
When doing a release with maven-release-plugin it will build the source again
when useReleaseProfile is true (use the release profile that adds sources and
javadocs to the released artifact).
The outcome is that it will run with both jar and jar-no-fork and generate and
deploy 2 -sources.jar artifacts, with same version. That makes the release
build fails.
The same behavior could be reproduced when running both jar and jar-no-fork
goal between maven 3.2.1. and maven 3.3.9.
----
Please find the logs for maven 3.2.1 and 3.3.9 in the foo.bar.zip
With maven 3.3.9 it uploads it 2 times :
Uploaded:
http://127.0.0.1:8081/nexus/content/repositories/releases/foo/bar/0.0.1/bar-0.0.1-sources.jar
(722 B at 15.3 KB/sec)
Uploading:
http://127.0.0.1:8081/nexus/content/repositories/releases/foo/bar/0.0.1/bar-0.0.1-sources.jar
722/722 B
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
