[
http://jira.codehaus.org/browse/MJAR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120500
]
nicolas de loof commented on MJAR-90:
-------------------------------------
A blank jar is never a good think. You will have a jar in your repo that is NOT
what it is expected to be, and can introduce strange issues when you come back
to your IDE. It also adds the risk to deploy an empty jar if your release goal
includes "deploy".
If you don't want to execute tests as part of the release process (I also do)
simply set <arguments>-Dmaven.test.skip.exec</arguments> in your POM for the
release plugin, or maybe in a parent corporate POM.
> when maven.test.Skip is set, the test-jar artifact is empty
> -----------------------------------------------------------
>
> Key: MJAR-90
> URL: http://jira.codehaus.org/browse/MJAR-90
> Project: Maven 2.x Jar Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: running any project with test-jar mojo
> Reporter: nicolas de loof
> Assignee: nicolas de loof
> Priority: Trivial
> Fix For: 2.2
>
>
> as maven.test.skip disable test compilation, the generated test-jar is empty.
--
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
