Hello Steve and others, there is actually also a bug report for a datatype which would be a fileset (or resource collection) associated with a mapper.
This would be the generic, clean solution to this kind of issues. Regards, Antoine > ------- Additional Comments From [EMAIL PROTECTED] 2006-11-21 07:37 > ------- > You know, I was trying to do this exact thing at work last week. Define a > fileset of files and then import it into both a tarfile and a zip file. > > Because I was using 1.7.0, it failed on me, even though I had the vague > idea > that it would work...I had to resort to duplicate declarations. If I had > used > ant1.6 it would have worked, and I too would have viewed the 1.7 behaviour > as a > regression. > > Putting aside the notion of immutable references, the underlying problem > is 'how > to add an existing fileset to a tar or zip file under a new path'. We > could do a > clean way that doesnt break the rules, and maybe resources already permit > it. > But since a way already did exist (possibly deliberately added in the > past), we > may just want to retain the old one. > > > Nb, regarding the extends attribute > > <zipfileset prefix="foo" extends-id="bar" /> > > That raises expecations too high, as you start thinking you can nest > > <zipfileset prefix="foo" extends-id="bar" > > <include name="*.class" /> > </zipfileset> > > A new resource may be better, one that doesnt take children. > > <zipfilesetref prefix="foo" refid="bar" /> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
