[MASSEMBLY-188] manifestEntries are not set in resulting jar

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.2-beta-2
• Environment: maven 2.0.5, windows/linux
• Assignee: John Dennis Casey
• Reporter: Vlad Skarzhevskyy
• Created: 04/Mar/07 10:00
• Updated: 01/Apr/08 05:34
• Resolved: 18/Feb/08 13:47

Description

archive manifestEntries are not set in resulting jar. even so the mainClass is set properly.
assembly format is jar

Example:
<configuration>
<attach>true</attach>
<appendAssemblyId>false</appendAssemblyId>
<descriptors>
<descriptor>assembly.xml</descriptor>
</descriptors>
<archive>
<manifest>
<mainClass>org.microemu.app.Main</mainClass>
</manifest>
<manifestEntries>
<Build-Number>${label}</Build-Number>
<Build-Time>${cctimestamp}</Build-Time>
</manifestEntries>
</archive>
</configuration>

full pom is here: http://microemulator.svn.sourceforge.net/viewvc/microemulator/trunk/microemulator/microemulator/

Issue Links

• duplicates: MASSEMBLY-121 Custom manifest attributres are ignored.