I've just reverted a portion of the change to distributionManagement
as it was breaking CI (you can't move things between objects).
I also find a few things weird about the order. IMO,
- dependencies and repositories should be together
- dependencies and dependencyManagement should be together
- build should be after dependencies, etc
- profiles should be after everything else.
Cheers,
Brett
On 29/06/2008, at 12:21 AM, Vincent Siveton wrote:
Hi,
FYI I created MNG-3634 and you could see the result here:
http://people.apache.org/~vsiveton/MNG-3634/maven-2.0.x/site/
maven.html
Comments are welcome!
Cheers,
Vincent
2008/6/23, Vincent Siveton <[EMAIL PROTECTED]>:
Hi,
I propose to improve [1] to add a code style for our pom files. As
the
following tags are required: modelVersion, groupId, artifactId and
version (see [2]), I see the following in this order.
<project>
<modelVersion/>
<parent/> if required
<groupId/>
<artifactId/>
<version/>
<name/>
<description/>
<prerequisites/> if required
<scm/>
<issueManagement/>
<dependencies/>
<build/> if required
<reporting/> if required
<profiles/> if required
<properties/> if required
</project>
My reasoning is mainly based on the consistency and the maintenance.
WDYT?
Vincent
[1] http://maven.apache.org/guides/development/guide-m2-development.html
[2]
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Minimal_POM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
