You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/12/28 19:52:55 UTC
[jira] Updated: (MSHADE-40) manifest data is lost when the shaded
result is a classifier.
[ http://jira.codehaus.org/browse/MSHADE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MSHADE-40:
------------------------------------
Attachment: pom.xml
Complete demo POM, works for me.
> manifest data is lost when the shaded result is a classifier.
> -------------------------------------------------------------
>
> Key: MSHADE-40
> URL: http://jira.codehaus.org/browse/MSHADE-40
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Benson Margulies
> Attachments: pom.xml
>
>
> I ran into problem with duplicate classes when I tried to use the shaded output of one project as an input to another shaded project, and they shared a dependency.
> So, I turned on the classifier feature, so that the second project could consume the unshaded version of the first one.
> And all is well, except that the Main-class: manifest attribute does not show up in the shaded jar.
> This works fine when I don't turn on the classifier. here's the POM-piece of note.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-shade-plugin</artifactId>
> <version>1.1</version>
> <configuration>
> <shadedArtifactAttached>true</shadedArtifactAttached>
> <finalName>excedrin-common-${common.version}</finalName>
> </configuration>
> <executions>
> <execution>
> <phase>package</phase>
> <goals>
> <goal>shade</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
--
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