[
http://jira.codehaus.org/browse/MASSEMBLY-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-121:
---------------------------------
Description:
Configure custom manifest entry in pom.xml
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.1</version>
<inherited>false</inherited>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>attached</goal>
</goals>
<configuration>
<descriptors>
<descriptor>${basedir}/src/main/assembly/install.xml</descriptor>
</descriptors>
<outputDirectory>${project.build.directory}</outputDirectory>
<workDirectory>${project.build.directory}/assembly/work</workDirectory>
<archive>
<manifest>
<mainClass>com.company.Install</mainClass>
</manifest>
<manifestEntries>
<mode>development</mode>
</manifestEntries>
</archive>
</configuration>
</execution>
</executions>
</plugin>
Custom manifest entry "mode" does not appear in jar manifest (although main
class entry does).
was:
Configure custom manifest entry in pom.xml
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.1</version>
<inherited>false</inherited>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>attached</goal>
</goals>
<configuration>
<descriptors>
<descriptor>${basedir}/src/main/assembly/install.xml</descriptor>
</descriptors>
<outputDirectory>${project.build.directory}</outputDirectory>
<workDirectory>${project.build.directory}/assembly/work</workDirectory>
<archive>
<manifest>
<mainClass>com.company.Install</mainClass>
</manifest>
<manifestEntries>
<mode>development</mode>
</manifestEntries>
</archive>
</configuration>
</execution>
</executions>
</plugin>
Custom manifest entry "mode" does not appear in jar manifest (although main
class entry does).
brian: What's the test you added? Is it an IT, or a unit test, or...? I'll
check this out, in addition to looking at the new patch.
> Custom manifest attributres are ignored.
> ----------------------------------------
>
> Key: MASSEMBLY-121
> URL: http://jira.codehaus.org/browse/MASSEMBLY-121
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: Windows XP SP2
> Java JDK 1.5.0_07
> Maven 2.0.4
> Reporter: Mark Reynolds
> Assignee: John Casey
> Fix For: 2.2-beta-2
>
> Attachments: assembly-plugin.patch, massembly121.zip
>
>
> Configure custom manifest entry in pom.xml
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <version>2.1</version>
> <inherited>false</inherited>
> <executions>
> <execution>
> <phase>package</phase>
> <goals>
> <goal>attached</goal>
> </goals>
> <configuration>
> <descriptors>
> <descriptor>${basedir}/src/main/assembly/install.xml</descriptor>
> </descriptors>
> <outputDirectory>${project.build.directory}</outputDirectory>
> <workDirectory>${project.build.directory}/assembly/work</workDirectory>
> <archive>
> <manifest>
> <mainClass>com.company.Install</mainClass>
> </manifest>
> <manifestEntries>
> <mode>development</mode>
> </manifestEntries>
> </archive>
> </configuration>
> </execution>
> </executions>
> </plugin>
> Custom manifest entry "mode" does not appear in jar manifest (although main
> class entry does).
--
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
