----- Original Message ----- From: "Jason van Zyl" <[EMAIL PROTECTED]> To: "Maven Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, October 08, 2003 8:30 AM Subject: RE: Moving Plugins
> > - also, now that plugins are externalized it will be more difficult to > > converge in term of jar versions between them. You may end up having to > > download 10 versions of log4j, etc. I believe we now need more urgently > > something like the discussed LATEST (which would point to the latest > > released jar): > > > > <dependency> > > <groupId>log4j</groupId> > > <artifactId>log4j</artifactId> > > <version>LATEST</version> > > </dependency> > > > > That would probably require the addition of some metadata file in the > > remote repo (releases.xml for ex), listing all releases. The default > > mode should not connect to internet every time maven builds but rather > > only connects on demand. > > We can probably borrow the SNAPSHOT logic and modify it for use with > LATEST. > If I may say something before it's too late: Maybe there is a need for a LATEST on each (or on several) branch (es). Something like <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>LATEST</version> </dependency> should get the latest-and-gratest, but something like <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.LATEST</version> </dependency> should use the latest version available that still has the version with prefix "1." Just a thought... Florin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
