Bug 34403 - zipgroupfileset should support a nested pattern specification
Summary: zipgroupfileset should support a nested pattern specification
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: 1.6.2
Hardware: Other other
: P2 normal with 2 votes (vote)
Target Milestone: ---
Assignee: Ant Notifications List
Depends on:
Reported: 2005-04-11 19:08 UTC by Kohsuke Kawaguchi
Modified: 2015-12-23 03:04 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Kohsuke Kawaguchi 2005-04-11 19:08:20 UTC
Just like the unzip task, the zipgroupfileset should support a nested pattern
set so that users can control which part of the source zip files should be
copied into the destination zip file.

This can be used to avoid having duplicate entries.
Comment 1 Wolfgang Brodowski 2006-04-26 12:52:20 UTC
Because of having problems with sign artefacts inside merged jar files using the
zipgroupfileset, i created a workaround (repackaging), which simulated the
missing "nested pattern specification" - maybe someone is interested in it:

<tempfile property="templib" destdir="@{destination}"/>
<move tofile="${templib}" file="${libraryname}"/>
<zip file="${libraryname}">
	<zipfileset src="${templib}">
		<exclude name="META-INF/*.SF"/>	
	<!-- EXAMPLE: excludes the existing sign information, which confuse
JavaWebstart -->
<delete file="${templib}" quiet="true"/>

put this snipped into a task and use it.
Comment 2 Stefan Bodewig 2008-11-21 06:12:58 UTC

*** This bug has been marked as a duplicate of bug 46257 ***
Comment 3 Hollis Waite 2015-12-23 03:04:42 UTC
zipgroupfileset should support two separate pattern specs: one to identify jar/zip files and another to filter files within jars/zips (e.g. META-INF/*).