Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
3.2.3
-
None
-
None
-
None
Description
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 http://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html#useReleaseProfile).
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
Attachments
Attachments
Issue Links
- duplicates
-
MNG-5868 Adding several times the same artifact via MavenProjectHelper (attachArtifact) keep adding to the List duplicate artifacts
- Closed
- is related to
-
MSHADE-195 createSourcesJar with source:jar-no-fork causes sources.jar to be deployed twice, causing the build to fail
- Closed