Given that enough support was expressed for enforcing the order of
pom.xml elements at build time rather than informally only, here is the
status of my investigation how this could be achieved.
The tidy:check goal was implemented in july 2014 [1], but there is no
release containing it yet. I asked for a release on
dev(a)mojo.codehaus.org, but I got no reply yet.
-- P
[1]
http://jira.codehaus.org/browse/MOJO-1945
On 2014-12-02 09:02, Thomas Segismont wrote:
Le 01/12/2014 19:14, mike thompson a écrit :
>
>> On 1 Dec 2014, at 09:00, Peter Palaga <ppalaga(a)redhat.com> wrote:
>>
>> Hi *,
>>
>> Apache has a convention [1] for $subj and there is a handy
>> tidy-maven-plugin [2] to fix the poms.
>>
>> It is often practical to have convention like this in place - esp.
>> when searching for a particular element in a pom file.
>>
>> Therefore, I'd like to propose to adopt this convention in rhq.next
>> projects. I would not enforce it at build time for now, I'd just
>> reorder all poms and document it at some appropriate place. WDYT?
>
> +1 on anything that programmatically enforces coding conventions.
> [Especially as more community members commit].
+1
>
>>
>> Thanks,
>>
>> Peter
>>
>> [1]
>>
http://maven.apache.org/developers/conventions/code.html#POM_Code_Convention
>>
>> [2]
http://mojo.codehaus.org/tidy-maven-plugin/
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel(a)lists.fedorahosted.org
>>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
>
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel