[ 
http://jira.codehaus.org/browse/MJAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153663#action_153663
 ] 

Tim Wood commented on MJAR-100:
-------------------------------

This issue is related: http://jira.codehaus.org/browse/MJAR-43

I think that if you can use the property described in this issue instead it 
will solve your problem: http://jira.codehaus.org/browse/SUREFIRE-129

-Dmaven.test.skip.exec



> Release preparation fails because jar plugin skips packaging of test jar
> ------------------------------------------------------------------------
>
>                 Key: MJAR-100
>                 URL: http://jira.codehaus.org/browse/MJAR-100
>             Project: Maven 2.x Jar Plugin
>          Issue Type: Bug
>         Environment: maven - 2.0.8
>            Reporter: Ashish Vashishta
>
> The release preparation goals fails when run with -DskipTests=true. The 
> failure occurs because the jar plugin doesn't create the *.tests.jar. The jar 
> plugin being used is 2.2.
> When same goal is run with previous jar plugin version (2.1), everything 
> works fine.
> The comparison of outputs from these two run indicate this behaviour.
> 1. When run with jar plugin version 2.2, following information is printed on 
> console
>     [INFO] [jar:jar]
>     [INFO] Building jar: D:\..\abc.jar
>     [INFO] [jar:jar {execution: default}]
>     [INFO] [jar:test-jar {execution: default}]
>     [INFO] Skipping packaging of the test-jar
> 2. While when run with jar plugin version 2.1, following information is 
> printed on console
>     [INFO] [jar:jar]
>     [INFO] Building jar: D:\..\abc.jar
>     [INFO] [jar:jar {execution: default}]
>     [INFO] [jar:test-jar {execution: default}]
>     [INFO] Building jar: D:\..\abc-tests.jar

-- 
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

        

Reply via email to