You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2010/01/17 15:22:55 UTC
[jira] Created: (MNG-4534) implement a preferred order for POM
elements
implement a preferred order for POM elements
--------------------------------------------
Key: MNG-4534
URL: http://jira.codehaus.org/browse/MNG-4534
Project: Maven 2 & 3
Issue Type: Wish
Components: POM
Affects Versions: 3.0-alpha-6
Reporter: Herve Boutemy
maven.mdo defines a de-facto order for POM XML elements, that is visible in [POM reference documentation|http://maven.apache.org/ref/2.2.1/maven-model/maven.html] or XML documents generated with [MavenXpp3Writer|http://maven.apache.org/ref/2.2.1/maven-model/apidocs/org/apache/maven/model/io/xpp3/MavenXpp3Writer.html].
The Maven team has voted during the end of June 2008 to follow [a specific POM convention to ordering POM elements|http://maven.apache.org/developers/conventions/code.html#POM_Code_Convention] to improve their readingness. The consequence of this vote is that the [Maven project descriptor|http://maven.apache.org/ref/2.2.1/maven-model/maven.html] is no more considered as the reference for the ordering.
With MODELLO-224 fixed in Modello 1.2, Maven's internal order can be configured in maven.mdo to match the POM convention: doing so would improve POM reference documentation (the convention is more intuitive than the actual de-facto order) and make MavenXpp3Writer implement the convention.
Note that this is only a *preferred* but *not enforced* order: POM elements order remains unchecked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4534) implement a preferred order for POM
elements
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MNG-4534.
------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-7
Assignee: Herve Boutemy
Modello plugin upgraded to 1.2 in r901562: the model has now a preferred order, which is followed by XML serialization and xdoc
> implement a preferred order for POM elements
> --------------------------------------------
>
> Key: MNG-4534
> URL: http://jira.codehaus.org/browse/MNG-4534
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: POM
> Affects Versions: 3.0-alpha-6
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Fix For: 3.0-alpha-7
>
>
> maven.mdo defines a de-facto order for POM XML elements, that is visible in [POM reference documentation|http://maven.apache.org/ref/2.2.1/maven-model/maven.html] or XML documents generated with [MavenXpp3Writer|http://maven.apache.org/ref/2.2.1/maven-model/apidocs/org/apache/maven/model/io/xpp3/MavenXpp3Writer.html].
> The Maven team has voted during the end of June 2008 to follow [a specific POM convention to ordering POM elements|http://maven.apache.org/developers/conventions/code.html#POM_Code_Convention] to improve their readingness. The consequence of this vote is that the [Maven project descriptor|http://maven.apache.org/ref/2.2.1/maven-model/maven.html] is no more considered as the reference for the ordering.
> With MODELLO-224 fixed in Modello 1.2, Maven's internal order can be configured in maven.mdo to match the POM convention: doing so would improve POM reference documentation (the convention is more intuitive than the actual de-facto order) and make MavenXpp3Writer implement the convention.
> Note that this is only a *preferred* but *not enforced* order: POM elements order remains unchecked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4534) implement a preferred order for POM
elements
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207209#action_207209 ]
Herve Boutemy commented on MNG-4534:
------------------------------------
maven.mdo modified in [r900146|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-model/src/main/mdo/maven.mdo?r1=895089&r2=900146&pathrev=900146&diff_format=h]
result will be available later, when Modello 1.2 is released and upgraded in Maven
> implement a preferred order for POM elements
> --------------------------------------------
>
> Key: MNG-4534
> URL: http://jira.codehaus.org/browse/MNG-4534
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: POM
> Affects Versions: 3.0-alpha-6
> Reporter: Herve Boutemy
>
> maven.mdo defines a de-facto order for POM XML elements, that is visible in [POM reference documentation|http://maven.apache.org/ref/2.2.1/maven-model/maven.html] or XML documents generated with [MavenXpp3Writer|http://maven.apache.org/ref/2.2.1/maven-model/apidocs/org/apache/maven/model/io/xpp3/MavenXpp3Writer.html].
> The Maven team has voted during the end of June 2008 to follow [a specific POM convention to ordering POM elements|http://maven.apache.org/developers/conventions/code.html#POM_Code_Convention] to improve their readingness. The consequence of this vote is that the [Maven project descriptor|http://maven.apache.org/ref/2.2.1/maven-model/maven.html] is no more considered as the reference for the ordering.
> With MODELLO-224 fixed in Modello 1.2, Maven's internal order can be configured in maven.mdo to match the POM convention: doing so would improve POM reference documentation (the convention is more intuitive than the actual de-facto order) and make MavenXpp3Writer implement the convention.
> Note that this is only a *preferred* but *not enforced* order: POM elements order remains unchecked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira