> It's crazy that version ranges are still unusable in 2.0.8.. I disagree entirely.
I use version ranges for a very complex Project... and it works very well * we have repeatable builds * we can mix and match snapshots during development if we need to * releases fail if you have snapshot deps even in ranges and transitions * this is all out of the box released maven core and plugins * have modules projects to test that the trunk of all projects builds and tests against the latest releases of all projects * have modules projects to test that the trunk of all projects builds and tests against the latest releases of all projects what more do you need? On Tue, 15 Jan 2008 06:41:42 Mark Hobson wrote: > On 10/01/2008, Michael McCallum <[EMAIL PROTECTED]> wrote: > > another thought... > > > > by default you could not have snapshot repositories enabled and just > > enable them with a profile... > > > > that way all builds by default have no snapshots, you could even have > > separate profiles and snapshot repos for different departments to a allow > > more flexible integration > > Unfortunately this won't work either due to > http://jira.codehaus.org/browse/MNG-2994 > > Both MNG-2994 and MNG-3092 need to be fixed before we can really start > using version ranges as they were intended. I think we should just > stick with the original design docs and apply the patch for MNG-3092. > > Cheers, > > Mark > > --------------------------------------------------------------------- > 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]
