That's awesome. Thanks. Quintin Beukes
On Mon, Oct 19, 2009 at 8:55 PM, Todd Thiessen <[email protected]> wrote: > The jars produced have the same, just different classifier. You simply > use the classifer tag when defining the dependency. ie: > > <groupId>a.b.c</groupId> > <artifactId>abc</artifactId> > <version>1.0</version> > <classifier>jdk1.4<\classifer> > > or > > <groupId>a.b.c</groupId> > <artifactId>abc</artifactId> > <version>1.0</version> > <classifier>jdk1.5<\classifer> > > --- > Todd Thiessen > > >> -----Original Message----- >> From: Quintin Beukes [mailto:[email protected]] >> Sent: Monday, October 19, 2009 2:48 PM >> To: Maven Users List >> Subject: Re: Config.jar project dependency >> >> >> OK, firstly you can only produce one artifact per POM. >> > This is not true. A POM has one GAV, but you can produce >> multiple artifacts with different classifiers. For example, >> most Java projects using the release plugin will have a >> source JAR file produced from the same POM and codebase. It >> has the same GAV, but an alternate classifier. >> >> That's very interesting. Could you perhaps point me in the >> right direction no how this would work. >> >> Lets say I make 2 jars with 2 separate classifiers, how to >> choose which one becomes a dependency of another project? >> >> Take Anders' case for example. Produce 2 jars "project1.jar" >> and "config.jar" from the same POM. How would he then include >> the config.jar as a dependency in another project? >> >> Q >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
