[ 
https://jira.codehaus.org/browse/MJAR-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MJAR-129.
-------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> Already build test-jar for project which packaging is not jar
> -------------------------------------------------------------
>
>                 Key: MJAR-129
>                 URL: https://jira.codehaus.org/browse/MJAR-129
>             Project: Maven JAR Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: java 1.6
> mvn 2.2.1, mvn 2.0.9, mvn 2.1.0
>            Reporter: Christophe Lallement
>         Attachments: test.zip
>
>
> The classic use case is when you use multi-module project.
> pomA  (packaging pom)
>   -> pomB (packaging jar)
>   -> pomC (packaging jar)
>   -> pomD (packaging pom)
> pomB,C,D inherit from pomA
> We define common plugin configuration into pomA, for example say to jar 
> plugin to build test jar.
> but in some case it make not sense (for example when pom is type of 'pom') 
> and in this case an empty jar is construct (then uploaded when we deploy)
> Maybe a check to detect zip file is empty could be sufficient or attache this 
> plugin only on specific pom packaging (jar/war/ear ...)
> I have attached a sample, just unzip and run mvn package inside "test" 
> directory.
> Regards
> Christophe



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to