How about dist.directory?
the idea behind the category/group was that it labeled the artifact with a property (eg, "shared", "tools") and that was then used as a key to determine the directory to deploy to in the dist via the additional property, eg dist.dependencies.categories=shared:lib,tools:tools/lib
are you proposing to specify the directory directly as a property of the artifact?
that is an option, although it is a bit less flexible, in that changing a directory path for a category implies changing it for each artfact in the project.xml and not a single change in the project.properties.
also, the approach of the label is a more open as it allows reuse for other scopes other than deciding where to deploy them in the dist.
Eg, I can have the need to sign some jars and not others, or
remove the version number for a specific category of jars that
get deployed in a separate directory.
Cheers
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
