On Sun, 2008-10-05 at 04:48 -0600, Michael McCallum wrote: > On Sat, 04 Oct 2008 14:16:57 Keith Branton wrote: > > 1. Can anyone please tell me of a way to achieve this with 2.0.9 today? > With the appropriate use of ranges you can do this and it resolves as > described. There are about 11 gotchas to doing it though, all worked around > by appropriate conventions.
Can you elaborate on what these 11 gotchas are, or point to a place which does? One of the biggest issues I see with ranges is that maven chooses the most recent version in the repository which matches a given range. Consequently, if a pom specifies a version range for a dependency like [1.5,), the exact same code can create different builds on different days if a new release of the dependency is made. I'm actually curious if anyone knows the reason for this; it seams that a far better choice would be to choose the *lowest* version which matches all range requirements, so that builds could be temporally stable. - Ian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
