[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041327#comment-15041327 ] chibbe commented on MNG-5939: - Its not hidden in (in some parent pom)? Im able to reproduce it with: {code:xml} org.apache.maven.plugins maven-source-plugin 2.4 attach-sources jar org.apache.maven.plugins maven-source-plugin 2.4 jar {code} And in effective pom I get: {code:xml} maven-source-plugin 2.4 jar attach-sources jar {code} > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037755#comment-15037755 ] chibbe commented on MNG-5939: - If it have both jar and jar-no-fork, it must be set by something in your super pom's etc.. The config I get it to work with is following, need to have the correct id. Run also into the same problem with javadoc's uploaded 2 times and failed so needed to have the same fix here as well. {code:xml} org.apache.maven.plugins maven-source-plugin 2.4 attach-sources jar org.apache.maven.plugins maven-javadoc-plugin 2.10.3 attach-javadocs package jar {code} > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037755#comment-15037755 ] chibbe edited comment on MNG-5939 at 12/3/15 1:08 PM: -- Both jar and jar-no-fork, it must be set by something in your super pom's etc.. I got it to work when I set the correct attach-sources|javadocs Run also into the same problem with javadoc's uploaded 2 times and failed so needed to have the same fix here as well. {code:xml} org.apache.maven.plugins maven-source-plugin 2.4 attach-sources jar org.apache.maven.plugins maven-javadoc-plugin 2.10.3 attach-javadocs package jar {code} was (Author: chibbe): If it have both jar and jar-no-fork, it must be set by something in your super pom's etc.. The config I get it to work with is following, need to have the correct id. Run also into the same problem with javadoc's uploaded 2 times and failed so needed to have the same fix here as well. {code:xml} org.apache.maven.plugins maven-source-plugin 2.4 attach-sources jar org.apache.maven.plugins maven-javadoc-plugin 2.10.3 attach-javadocs package jar {code} > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037755#comment-15037755 ] chibbe edited comment on MNG-5939 at 12/3/15 1:47 PM: -- Both jar and jar-no-fork, it must be set by something in your super pom's etc.. I got it to work when I set the correct attach-sources|javadocs Run also into the same problem with javadoc's uploaded 2 times and failed so needed to have the same fix here as well. {code:xml} org.apache.maven.plugins maven-source-plugin 2.4 attach-sources jar org.apache.maven.plugins maven-javadoc-plugin 2.10.3 attach-javadocs jar {code} was (Author: chibbe): Both jar and jar-no-fork, it must be set by something in your super pom's etc.. I got it to work when I set the correct attach-sources|javadocs Run also into the same problem with javadoc's uploaded 2 times and failed so needed to have the same fix here as well. {code:xml} org.apache.maven.plugins maven-source-plugin 2.4 attach-sources jar org.apache.maven.plugins maven-javadoc-plugin 2.10.3 attach-javadocs package jar {code} > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035402#comment-15035402 ] chibbe commented on MNG-5939: - I guess it will solve the problem when doing a release. But will there be any -sources.jar file built and deployed in a normal build (not running release build)? I tested to run the jar goal instead of jar-no-fork, and that also fixed the problem for us. > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chibbe updated MNG-5939: Affects Version/s: 3.3.3 > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028536#comment-15028536 ] chibbe commented on MNG-5939: - As you can see in the foo.bar.zip there is no parent pom. The exact same code, but different behavior. > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028678#comment-15028678 ] chibbe commented on MNG-5939: - The first version it was introduced was 3.2.3 two -sources.jar . older maven versions only creates one -sources.jar. > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028795#comment-15028795 ] chibbe commented on MNG-5939: - The reason with both 2 goals was only to easy be able to reproduce the problem. As you see in the foo.bar.zip/foo.bar/maven-3.2.1.log it only deploys 1 sources file and build is fine. In maven-3.3.9.log the exact same code is executed but here the build is failing. -- In our configuration we have only jar-no-fork goal. And when doing an release:perform it will create the sources as well[1]. So maven tries to deploy the source two times and it makes the build fail. If only defining the the jar goal[2], will also solve the issue. So question is.. Was it a bug before 3.2.3 that is now fixed or is it a bug that was introduced in 3.2.3? [1] - http://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html#useReleaseProfile [2] - https://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html > 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.3, 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-5939) Problem doing release when sources are generate as well
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)
[jira] [Updated] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chibbe updated MNG-5939: Attachment: foo.bar.zip Example project. Including logs from both maven 3.2.1 and 3.3.9 > 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 > Attachments: foo.bar.zip > > > 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)
[jira] [Updated] (MNG-5939) Problem doing release when sources are generate as well
[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chibbe updated MNG-5939: 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 was: 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 > 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 > Attachments: foo.bar.zip > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHADE-195) createSourcesJar with source:jar-no-fork causes sources.jar to be deployed twice, causing the build to fail
[ https://issues.apache.org/jira/browse/MSHADE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026892#comment-15026892 ] chibbe commented on MSHADE-195: --- Also able to reproduce this behavior with maven 3.3.9 worked with maven 3.2.1. maven-release-plugin:2.5.2 maven-source-plugin:2.4 But shouldn't this be a ticket for release maven-release-plugin or maven-source-plugin. > createSourcesJar with source:jar-no-fork causes sources.jar to be deployed > twice, causing the build to fail > --- > > Key: MSHADE-195 > URL: https://issues.apache.org/jira/browse/MSHADE-195 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 >Reporter: Esko Luontola > Fix For: waiting-for-feedback, 2.4.3 > > Attachments: MSHADE-195-example.zip > > > The workaround described in https://issues.apache.org/jira/browse/MSHADE-120 > (i.e. running maven-source-plugin's jar-no-fork goal before shading) causes > the problem that Maven will install and deploy the same sources.jar file > twice: > {noformat} > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ > pricing-client --- > [INFO] Installing xxx/pricing-client/target/pricing-client-0-SNAPSHOT.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.jar > [INFO] Installing xxx/pricing-client/target/dependency-reduced-pom.xml to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.pom > [INFO] Installing > xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar > [INFO] Installing > xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar > {noformat} > With maven-install-plugin this doesn't matter that much, but with > maven-deploy-plugin it *fails the build*, because it tries to upload the > sources.jar twice to the Maven repository and _Nexus doesn't allow that_: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project project: Failed to deploy artifacts: Could not transfer artifact > xxx.availability:availability-client:jar:sources:1.0.24 from/to xxx-releases > (http://xxx/nexus/content/repositories/releases): Failed to transfer file: > http://xxx/nexus/content/repositories/releases//availability/availability-client/1.0.24/availability-client-1.0.24-sources.jar. > Return code is: 400, ReasonPhrase: Bad Request. > {noformat} > I'm suspecting this to be something like the maven-source-plugin and > maven-shade-plugin both attaching the same sources.jar to the build, when > only one of them should do it. This problem only happens with the sources jar > and not the main artifact, so a trick similar to replacing the main artifact > is needed also for the sources jar. > h4. Workaround > Configure maven-source-plugin with {{false}}. Then the shade > plugin will find the sources and include them in the shaded sources jar, but > the sources jar won't be attached to the build twice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MSHADE-195) createSourcesJar with source:jar-no-fork causes sources.jar to be deployed twice, causing the build to fail
[ https://issues.apache.org/jira/browse/MSHADE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026892#comment-15026892 ] chibbe edited comment on MSHADE-195 at 11/25/15 3:05 PM: - Also able to reproduce this behavior with maven 3.3.9 worked with maven 3.2.1. maven-release-plugin:2.5.2 maven-source-plugin:2.4 But shouldn't this be a issue for release maven-release-plugin or maven-source-plugin. was (Author: chibbe): Also able to reproduce this behavior with maven 3.3.9 worked with maven 3.2.1. maven-release-plugin:2.5.2 maven-source-plugin:2.4 But shouldn't this be a ticket for release maven-release-plugin or maven-source-plugin. > createSourcesJar with source:jar-no-fork causes sources.jar to be deployed > twice, causing the build to fail > --- > > Key: MSHADE-195 > URL: https://issues.apache.org/jira/browse/MSHADE-195 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 >Reporter: Esko Luontola > Fix For: waiting-for-feedback, 2.4.3 > > Attachments: MSHADE-195-example.zip > > > The workaround described in https://issues.apache.org/jira/browse/MSHADE-120 > (i.e. running maven-source-plugin's jar-no-fork goal before shading) causes > the problem that Maven will install and deploy the same sources.jar file > twice: > {noformat} > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ > pricing-client --- > [INFO] Installing xxx/pricing-client/target/pricing-client-0-SNAPSHOT.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.jar > [INFO] Installing xxx/pricing-client/target/dependency-reduced-pom.xml to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.pom > [INFO] Installing > xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar > [INFO] Installing > xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar > {noformat} > With maven-install-plugin this doesn't matter that much, but with > maven-deploy-plugin it *fails the build*, because it tries to upload the > sources.jar twice to the Maven repository and _Nexus doesn't allow that_: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project project: Failed to deploy artifacts: Could not transfer artifact > xxx.availability:availability-client:jar:sources:1.0.24 from/to xxx-releases > (http://xxx/nexus/content/repositories/releases): Failed to transfer file: > http://xxx/nexus/content/repositories/releases//availability/availability-client/1.0.24/availability-client-1.0.24-sources.jar. > Return code is: 400, ReasonPhrase: Bad Request. > {noformat} > I'm suspecting this to be something like the maven-source-plugin and > maven-shade-plugin both attaching the same sources.jar to the build, when > only one of them should do it. This problem only happens with the sources jar > and not the main artifact, so a trick similar to replacing the main artifact > is needed also for the sources jar. > h4. Workaround > Configure maven-source-plugin with {{false}}. Then the shade > plugin will find the sources and include them in the shaded sources jar, but > the sources jar won't be attached to the build twice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MSHADE-195) createSourcesJar with source:jar-no-fork causes sources.jar to be deployed twice, causing the build to fail
[ https://issues.apache.org/jira/browse/MSHADE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026892#comment-15026892 ] chibbe edited comment on MSHADE-195 at 11/25/15 3:05 PM: - Also able to reproduce this behavior with maven 3.3.9 worked with maven 3.2.1. maven-release-plugin:2.5.2 maven-source-plugin:2.4 But shouldn't this be a issue for maven-release-plugin or maven-source-plugin. was (Author: chibbe): Also able to reproduce this behavior with maven 3.3.9 worked with maven 3.2.1. maven-release-plugin:2.5.2 maven-source-plugin:2.4 But shouldn't this be a issue for release maven-release-plugin or maven-source-plugin. > createSourcesJar with source:jar-no-fork causes sources.jar to be deployed > twice, causing the build to fail > --- > > Key: MSHADE-195 > URL: https://issues.apache.org/jira/browse/MSHADE-195 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 2.3, 2.4 >Reporter: Esko Luontola > Fix For: waiting-for-feedback, 2.4.3 > > Attachments: MSHADE-195-example.zip > > > The workaround described in https://issues.apache.org/jira/browse/MSHADE-120 > (i.e. running maven-source-plugin's jar-no-fork goal before shading) causes > the problem that Maven will install and deploy the same sources.jar file > twice: > {noformat} > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ > pricing-client --- > [INFO] Installing xxx/pricing-client/target/pricing-client-0-SNAPSHOT.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.jar > [INFO] Installing xxx/pricing-client/target/dependency-reduced-pom.xml to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT.pom > [INFO] Installing > xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar > [INFO] Installing > xxx/pricing-client/target/pricing-client-0-SNAPSHOT-sources.jar to > xxx/pricing-client/0-SNAPSHOT/pricing-client-0-SNAPSHOT-sources.jar > {noformat} > With maven-install-plugin this doesn't matter that much, but with > maven-deploy-plugin it *fails the build*, because it tries to upload the > sources.jar twice to the Maven repository and _Nexus doesn't allow that_: > {noformat} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project project: Failed to deploy artifacts: Could not transfer artifact > xxx.availability:availability-client:jar:sources:1.0.24 from/to xxx-releases > (http://xxx/nexus/content/repositories/releases): Failed to transfer file: > http://xxx/nexus/content/repositories/releases//availability/availability-client/1.0.24/availability-client-1.0.24-sources.jar. > Return code is: 400, ReasonPhrase: Bad Request. > {noformat} > I'm suspecting this to be something like the maven-source-plugin and > maven-shade-plugin both attaching the same sources.jar to the build, when > only one of them should do it. This problem only happens with the sources jar > and not the main artifact, so a trick similar to replacing the main artifact > is needed also for the sources jar. > h4. Workaround > Configure maven-source-plugin with {{false}}. Then the shade > plugin will find the sources and include them in the shaded sources jar, but > the sources jar won't be attached to the build twice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (MDEP-479) Find duplicate properties
[ https://jira.codehaus.org/browse/MDEP-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=364020#comment-364020 ] chibbe ... commented on MDEP-479: - I set all version(s) for dependencies as properties, and sometimes when many dependencies and properties there has been duplicates. Want some way to catch this fault(s). Attached a pom.xml with duplicated property. Find duplicate properties - Key: MDEP-479 URL: https://jira.codehaus.org/browse/MDEP-479 Project: Maven Dependency Plugin Issue Type: New Feature Reporter: chibbe ... Fix For: waiting-for-feedback Attachments: pom.xml Would be good if a used property duplicated properties can be found as well. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-479) Find duplicate properties
[ https://jira.codehaus.org/browse/MDEP-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chibbe ... updated MDEP-479: Attachment: pom.xml Find duplicate properties - Key: MDEP-479 URL: https://jira.codehaus.org/browse/MDEP-479 Project: Maven Dependency Plugin Issue Type: New Feature Reporter: chibbe ... Fix For: waiting-for-feedback Attachments: pom.xml Would be good if a used property duplicated properties can be found as well. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-479) Find duplicate properties
chibbe ... created MDEP-479: --- Summary: Find duplicate properties Key: MDEP-479 URL: https://jira.codehaus.org/browse/MDEP-479 Project: Maven Dependency Plugin Issue Type: New Feature Reporter: chibbe ... Would be good if a used property duplicated properties can be found as well. -- This message was sent by Atlassian JIRA (v6.1.6#6162)