Exactly, ranges are evil for release builds On Monday, 21 October 2013, Jesse Glick wrote:
> On Mon, Oct 21, 2013 at 12:45 PM, Vincent Latombe > <[email protected] <javascript:;>> wrote: > > Probably caused by http://jira.codehaus.org/browse/MNG-3092 > > which makes snapshot versions selected as part of version ranges. > > Right. Moral of the story: do not use version ranges. > > (They are pretty pointless in Maven anyway, since a given project may > only have one version of a given dependency, and various declared > dependency versions will frequently clash. No system presuming a flat > classpath and automatic transitive dependencies could really do > better. Only an actual Java module system like OSGi can properly > express such constraints, and the build tool would need to be aware of > the module system to some extent.) > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:;>. > For more options, visit https://groups.google.com/groups/opt_out. > -- Sent from my phone -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
