Currently you can only create a jar from actual files. There are times in my
build process where I need to merge parts of one jar with parts of another
to create a new jar. What I currently must do is extract those files into
the file system in a temp dir, then jar them up.
Perhaps I'm missing something and there's a better way to do the above, but
it would be cool if filesets could take in a "jar" (or zip/tar/war) instead
of just a "dir". the syntax would otherwise be the same for the <fileset>,
eg.
<jar jarfile="${staging.ear}/wamnet.jar">
<fileset dir="${classes.source}">
<exclude name="**/*TEST.class"/>
<exclude name="com/wamnet/transport/psd/*"/>
<exclude name="com/wamnet/transport/uploadservlet/*"/>
</fileset>
<fileset jar="${lib.dir}/WamMisc.jar">
<include name="/com/wamnet/tools/**"/>
</fileset>
</jar>
the second fileset would just extract the included files from the jar
archive and those would be included in the jarfile.
while I'm on the subject, the <unjar|unwar|unzip> tasks should allow nested
<include> and <exclude> tags, though executing a <copy> with a <filset jar=>
would be essentially the same as this.
Tim
