When you reorder, you should be able to do a -DdryRun and let it produce for you a "pom.xml.reorder" file.
And when you run the reordering for real, let it create a "pom.xml.backup" Hey, doesn't this sound just like the philosophy of the release plugin? :-) Paul On Tue, Jul 1, 2008 at 11:26 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > >I understand your concerns, but the same issue can happen when adding or > >removing a dependency, not just reordering. I would rather recommend that > >people rely on dependency management to control transitive versions than > rely on > >the order in the pom. Then you should be able to organize deps in your > pom > >anyway you want. > > As would I, but allowing people to completely hose their build for no good > reason isn't a good idea. At a minimum, this goal should back up the > existing pom and give a stern warning that they may get build or runtime > issues by doing this. Remember, the issue may not show up immediately but > only later at runtime. >
