In order to have a stable system you MUST understand what the latest release means... if you introduce this into your build you have no control over what actually ends up in it. As an end user this is not a huge deal directly except when people start using RELEASE/STABLE in libraries in the main repositories....
What is the latest "STABLE" release? it really depends on your use case. Perhaps a better solution would be to add more metadata into the repository releated to outstanding issues in jira for a particular release. You could then say i would like the latest build with no bugs or critical issues or just no critical issues With RELEASE you end up using the latest released code of every project and the shit hits the fan, you might as well build all the projects from source yourself! i vote a big (non binding ;-) -1 for MNG-2431 if you really want to have an unstable project then use the [0,) range but don't encourage people with nice looking tags... On Tue, 22 Jan 2008 02:32:28 Tomasz Pik wrote: > On Jan 21, 2008 2:21 PM, Guillaume Lederrey > > <[EMAIL PROTECTED]> wrote: > > On 20/01/2008, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > > You can use dependencyManagment in a parent pom to avoid specifying the > > > version in all your child poms. If you really want the "latest" you > > > have two choices: > > > LATEST - latest snapshot > > > RELEASE - latest release > > > > > > Or you could specify a range like [0,) > > > > Probably a dummy question on my part : I can get ranges to work, but > > not RELEASE nor LATEST. If y put the version of a dependency to > > either, I get : > > > > > > [INFO] Failed to resolve artifact. > > > > Missing: > > ---------- > > 1) myGroup:myProject:jar:RELEASE > > > > > > And the usual "dependency not found, would you like to install it" > > message. > > > > I tried to find docs, but found not much. Do you know since which > > version of maven this is available ? > > As far as I know it works only for plugins. > For general usage - please, vote here, maybe this issue will get > some attention: > http://jira.codehaus.org/browse/MNG-2431 > > Regards, > Tomek > > > Thanks ! > > > > > -----Original Message----- > > > From: amit kumar [mailto:[EMAIL PROTECTED] > > > Sent: Friday, January 18, 2008 8:38 AM > > > To: Maven Users List > > > Subject: Avoid Dependency version > > > > > > Hi, > > > Can I make it possible for my dependencies(jar files) declared in > > > <dependency> tags, not have version. Just like in case of plugin it > > > happens, > > > the latest on gets fetched? > > > When I don't put a version in my dependency tag, it throws error. > > > > > > Regards, > > > Amit > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > > Jabber : [EMAIL PROTECTED] > > Skype : Guillaume.Lederrey > > Projects : > > * http://rwanda.wordpress.com/ > > * http://rwandatech.wordpress.com/ > > > > > > --------------------------------------------------------------------- > > 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] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
