2. Once you have a repository, you need to extract files from it for use in WAR files, etc. Which means (a) a library policy to create a fileset from the collection
(b) <lib> in WAR/EAR must flatten filesets during copy.
No, you need a flattening mapper - but only if you need to copy the libraries. There may be sound reasons for preserving a hierarchy in a WAR/EAR. For most purposes, <flattenmapper> should suffice. I have defined a <depencies-mapper> which also strips version numbers in case the target has hard-coded its jar dependencies ad doesn't want the names to change with new versions.
I can't think of any sound reasons for preserving hierarchy in WEB-INF/lib.
I would very much like to see the <lib> element flatten, or some way to flatten any arbitrary fileset. I end up doing a <copy> to flatten a hierarchical directory before using <lib>, which is sub-optimal.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
