I'm thinking maybe what we need here [1] is a way to wrap arbitrary resource collections with archival information, like extracting the archive attribute getters of ArchiveFileSet to an ArchivalResourceCollection interface, implemented by ArchiveFileSet as well as sugg. ArchivalResources which would take any embedded Resource(s)... then filelists or explicit <file> resources could be used (these should fail if missing I think). Then to create archives, archival tasks would look not for ArchiveFileSet per se but ArchivalResourceCollection or ArchiveInput or whatever we want to call it. What holes have I missed in this approach?
-Matt [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=32526 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
