Maven uses classifiers for this "flavoring" concept. The default naming is groupId/artifactId-version-classifier.packaging. So in your example, it would be product-1.0-obfuscated.jar, and the dependency declaration would be:
<dependency> <groupId>name</groupId> <artifactId>product</artifactId> <version>1.0</version> <classifier>obfuscated</classifier> </dependency> Wayne On 9/25/07, Richard Chamberlain <[EMAIL PROTECTED]> wrote: > Hi There, > > > > I'm just porting a build to maven2, and I'm wondering what is the best > way to produce different flavours of an application. > > > > For example we produce different versions of a jar: optimized, debug and > obfuscated. (sometimes for different versions of java) > > > > All 3 are built in one build cycle and I'd like to deploy them into the > repository under the same version. > > e.g. > > > > name/product/1.0/jar-optimsed-1.0.jar > > name/product/1.0/jar-debug-1.0.jar > > name/product/1.0/jar-obfuscated-1.0.jar > > > > Is this the correct way to distribute different versions? > > > > Thanks for the help, > > Richard Chamberlain > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
