You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/03/03 23:08:29 UTC

[jira] Commented: (MSHADE-20) Take care of Manifest attributes defined in maven-jar-plugin

    [ http://jira.codehaus.org/browse/MSHADE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125971 ] 

Brett Porter commented on MSHADE-20:
------------------------------------

what version were you using? It would be best checked against a release instead of trunk

I just tried this on maven-core using the 1.0 release and it worked as expected.

> Take care of Manifest attributes defined in maven-jar-plugin
> ------------------------------------------------------------
>
>                 Key: MSHADE-20
>                 URL: http://jira.codehaus.org/browse/MSHADE-20
>             Project: Maven 2.x Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Vincent Siveton
>
> Using the following in the POM
> {code:xml} 
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-jar-plugin</artifactId>
>         <configuration>
>           <archive>
>             <manifest>
>               <mainClass>MyMainClass</mainClass>
>               ...
>             </manifest>
>           </archive>
>         </configuration>
>       </plugin>
> {code} 
> The manifest in the generated artifact has a Main-Class attribute but it is not present in the *uber.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