The issue is that the order of dependencies does matter. Resolving transitive dependencies is based on how near the dependency is to the pom and the order in which dependencies are listed...
Listing them in alpha order, if you've always done this is fine and won't change your build (as you've always done so) but if you now change the order to random order, because the resolution of transitive dependencies uses the order dependencies are listed in the pom as the penalty-shoot-out, your build _may_ pull in different dependencies. Actually, penalty shoot out is probably not the best analogy, more like number of away goals... you've matched on points, you've matched on goal difference, you've matched on away wins and the only thing left to decide who wins the league is away goals. Personally, I think if Maven can provide a warning when your build is resolving dependencies based on dependency order in a pom, that would be a _good thing_ -Stephen On Thu, Jul 3, 2008 at 4:37 AM, Paul Benedict <[EMAIL PROTECTED]> wrote: > I must have missed something in the discussion. Please forgive my ignorance > here, but why is so much discussion happening on reordering the > dependencies? Honestly, they shouldn't be reordered. I list out my > dependencies in pure alphabetical order by group and artifact, and I > wouldn't want those messed with when I clean up the POM. > > Paul > > On Wed, Jul 2, 2008 at 1:58 PM, Brian E. Fox <[EMAIL PROTECTED]> > wrote: > >> >> >If people want to hose their build, there is not much we can do to stop >> them ;) >> >Are you thinking that this dependency sort would run automatically during >> the >> >release process? I was imagining this used during the development cycle, >> so >> >that any changes it causes would go through some cycles of testing. >> Obviously, >> >I would be very concerned if something like this was run during the >> release process. >> >> I'm concerned that we're just giving people a loaded gun that we hope they >> don't shoot themselves with...particularly when the end result didn't really >> do much useful other than pretty up their source. If the tool can somehow >> analyze the transitive results of the changes, great. Actually I think this >> part of the tool might be the best piece to have so you can analyze results >> across any pom changes, not just sorting. >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
