[
http://jira.codehaus.org/browse/MSHADE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSHADE-20:
--------------------------------
Attachment: MSHADE-20-reworked.diff
I tested your patch on doxia-converter
AFAIK, the problem is that the manifest entry is not in the original jar file:
the Main-Class entry is added in the assembly
here is a modified patch to add the entry in the original jar, and then
everything is ok either with shade plugin 1.0 or 1.1-SNAPSHOT
can you confirm?
> 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
> Attachments: MSHADE-20-reworked.diff, MSHADE-20.diff
>
>
> 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
