[
http://jira.codehaus.org/browse/MNG-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176771#action_176771
]
Sami Dalouche commented on MNG-4160:
------------------------------------
BTW, keeping the exact same assembly description, release mechanism, but
removing the dependency from the "integration-tests" module to the
"client:tests" module (classifier:tests, scope: test) fixes the generated
assembly :
http://www.sirika.com/maven2/releases/com/sirika/pymager/pymager-java-client-assembly/0.10/pymager-java-client-assembly-0.10-all.zip
so, the problem might lie in the assembly dependencySet resolution mechanism..
But still no idea why it would only happen during a release.. does the
release:perform pass any kind of weird flag while running the assembly goal ?
(the assembly plugin is attached to the assembly module's package goal)
regards,
Sami
> maven test-jar, assembly and release plugins don't play well together
> ---------------------------------------------------------------------
>
> Key: MNG-4160
> URL: http://jira.codehaus.org/browse/MNG-4160
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Sami Dalouche
> Attachments: log
>
>
> Problem: in some weird cases, maven assembly plugin seems to pick the -tests
> dependency instead of the main one.
> How to reproduce:
> Consider the given project :
> http://www.sirika.com/maven2/releases/com/sirika/pymager/pymager-java-client-assembly/0.9/pymager-java-client-assembly-0.9-all.zip
> the source of the project, along with the maven POMs are in the src/
> directory.
> the .zip is the result of running the mvn -Prelease release:prepare
> -DautoVersionSubmodules=true && mvn release:perform
> Take a look at the file lib/pymager-java-client-0.9.jar in the archive.
> Now, take the source and run
> mvn -Prelease package
> unzip assembly/target/assembly/target/out/pymager-java-client-0.9.zip
> and take a look at lib/pymager-java-client-0.9.jar
> the file is different from the one that was created using the release:perform
> !!!
> In the case of the release, it corresponds to the pymager-java-client:tests
> artifact, instead of the main pymager-java-client artifact.
> everything seems to run OK outside of a release..
> ouch!
> good luck....
> Sami Dalouche
> ( I attached the log of running mvn -Pdev clean install, so that you get my
> OS and JDK version)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
