Hi folks,

As i lazy user, i would like the automatic ordering to write things
in a specific order: first come the things that have the greater
chance to be changed/read,
and then go to the end of the file with things that are not relevant
for a reader/modifier
ending with modelVersion.

my 2 cents

Raphaël

2008/6/24 John Casey <[EMAIL PROTECTED]>:
> It would probably be a good idea to reorder the fields in the maven.mdo file
> inside the maven-model project, to reflect the preferred style. This should
> have the effect of reordering the generated reference documentation and will
> also affect the ordering achieved when a POM is written programmatically
> using the xpp3 writer (I think).
>
> -john
>
> Benjamin Bentmann wrote:
>>
>> Vincent Siveton schrieb:
>>
>>> I propose to improve [1] to add a code style for our pom files.
>>
>> +1 for some convention (which is documented as such).
>>
>>> I see the following in this order.
>>
>> Considering other POMs like parent POMs and Mojo, your proposal should
>> finally cover all POM elements (e.g. <packaging>, <url>, <licenses>,
>> <developers> etc.).
>>
>> Whatever we agree upon, we might want to update the Maven Model Reference
>> [0], too. I guess that was the ordering Dennis has chosen.
>>
>> If not already written down, the indentation style (2 spaces) should be
>> mentioned, too.
>>
>>> <project>
>>>  ...
>>> </project>
>>
>> I find your proposed ordering more intuitive than the current Model Ref.
>>
>>
>> Benjamin
>>
>>
>> [0] http://maven.apache.org/ref/current/maven-model/maven.html
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to