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

Falko Modler edited comment on MJAR-139 at 1/14/11 4:50 AM:
------------------------------------------------------------

I'd prefer the addition of the skip parameter for jar:jar.

Adding another packaging might be too "invasive"...

      was (Author: famod):
    I'd prefer the addition of the skip parameter for jar:jar.

Adding another packing might be too "invasive"...
  
> New option to avoid empty jar creation
> --------------------------------------
>
>                 Key: MJAR-139
>                 URL: http://jira.codehaus.org/browse/MJAR-139
>             Project: Maven 2.x Jar Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.1
>            Reporter: Roman Ivanov
>
> Usage of "test-jar" is beneficial for all project, as all of them have tests.
> <plugin>
>       <groupId>org.apache.maven.plugins</groupId>
>       <artifactId>maven-jar-plugin</artifactId>
>       <version>2.3.1</version>
>       <executions>
>           <execution>
>                       <goals>
>                           <goal>test-jar</goal>
>                       </goals>
>           </execution>
>       </executions>
> </plugin>
> Pom artifacts and some jar artifacts does not have test and will never have 
> them.
> In logs we have: "[WARNING] JAR will be empty - no content was marked for 
> inclusion!"
> and empty and useless artifacts are created, deployed , ...
> It will be convenient to have an plugin option to define whether skip empty 
> jar creation and warning or generate jar with warning in log. Does it make 
> sense ?
> By default option will be FALSE, to comply with previous behavior.

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