RE: [Proposal] Pom Code Style (WAS svn commit: r670264 - /maven/plugins/trunk/maven-site-plugin/pom.xml)

>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.