https://issues.apache.org/bugzilla/show_bug.cgi?id=54171
Bug ID: 54171
Summary: <jar> filesetmanifest="mergewithoutmain" only works
when <manifest> provided
Product: Ant
Version: 1.8.2
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
Assignee: [email protected]
Reporter: [email protected]
Classification: Unclassified
Similar to bug 29731, except that the broken behavior only exposes itself when
<manifest> is not provided within a <jar> task.
jar1.jar's manifest:
Manifest-Jar1: This is the MAIN part of jar1's Manifest
Name: jar1
SomeProperty: Property of Jar1
jar2.jar's manifest:
Manifest-Jar2: This is the MAIN part of jar2's Manifest
Name: jar2
SomeProperty: Property of Jar2
build.xml:
<project name="test" default="build" basedir=".">
<target name="build">
<jar destfile="broken.jar" filesetmanifest="mergewithoutmain">
<zipgroupfileset dir=".">
<include name="jar1.jar"/>
<include name="jar2.jar"/>
</zipgroupfileset>
</jar>
<jar destfile="working.jar" filesetmanifest="mergewithoutmain">
<manifest/>
<zipgroupfileset dir=".">
<include name="jar1.jar"/>
<include name="jar2.jar"/>
</zipgroupfileset>
</jar>
</target>
</project>
Working.jar will have the expected manifest, since there was a <manifest>
section in the <jar> task. Broken.jar will behave as if filesetmanifest="merge"
and include main elements from jar1 and jar2
Obvious work-around to issue is to provide an empty <manifest/> section.
--
You are receiving this mail because:
You are the assignee for the bug.
