[jira] Closed: (MASSEMBLY-441) manifest is incorrectly 'overwritten' when using jar-with-dependencies

["John Casey (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MASSEMBLY-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MASSEMBLY-441.
--------------------------------

       Resolution: Won't Fix
    Fix Version/s: 2.2-beta-6
         Assignee: John Casey

you can configure the assembly plugin to produce manifests in the same manner as the jar plugin:

http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
http://maven.apache.org/plugins/maven-jar-plugin/examples/default-manifest-file.html
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html


> 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
>             Fix For: 2.2-beta-6
>
>
>             <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