[ http://jira.codehaus.org/browse/MASSEMBLY-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-441: -------------------------------------- Fix Version/s: (was: 2.2) > manifest is incorrectly 'overwritten' when using jar-with-dependencies > ---------------------------------------------------------------------- > > Key: MASSEMBLY-441 > URL: http://jira.codehaus.org/browse/MASSEMBLY-441 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug > Affects Versions: 2.2-beta-4 > Environment: Maven 2.1 > JDK 1.5 > Reporter: Adrian Shum > Assignee: John Casey > > <plugin> > <artifactId>maven-assembly-plugin</artifactId> > <configuration> > <descriptorRefs> > <descriptorRef>jar-with-dependencies</descriptorRef> > </descriptorRefs> > <archive> > <manifest> > > <mainClass>my.fullly.qualified.MainClass</mainClass> > </manifest> > </archive> > </configuration> > <executions> > <execution> > <id>make-assembly</id> > <phase>package</phase> > <goals> > <goal>directory</goal> <!-- same case when > using single --> > </goals> > </execution> > </executions> > </plugin> > I used the plugin config above and tried to create a 'all-in-one executable > jar'. > However, I found the MANIFEST.MF is not really what I declared. > It seems that MANIFEST.MF of certain dependencies JARs is put there instead > (In my case, Oracle's JDBC driver JAR's MANIFEST.MF is presented) -- 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