[ http://jira.codehaus.org/browse/MNG-1890?page=comments#action_54013 ]
Olivier Lamy commented on MNG-1890:
-----------------------------------
You can easily do it with a super pom which includes all your commons
dependencies.
Then use this in your others poms.
<parent>
<groupId>groupId</groupId>
<artifactId>commons-root-pom</artifactId>
<version>version</version>
</parent>
> Optionally split up/partition pom.xml with XInclude
> ---------------------------------------------------
>
> Key: MNG-1890
> URL: http://jira.codehaus.org/browse/MNG-1890
> Project: Maven 2
> Type: Improvement
> Components: POM
> Versions: 2.0.1
> Reporter: Geoffrey
>
>
> A pom.xml can get really big, considering it holds more information then
> maven.xml and project.xml together.
> In Java is a bad idea to have a class with more then 500 lines.
> In Spring they use the <import tag to split up applicationContext files.
> But there already is a standard to partition xml files: XInclude.
> From a user perspective a partitioned pom.xml would be a lot more maintable
> since we could decide to make a
> pom-dependencies.xml etc if we we want.
> Problems:
> - Sending the pom to the repository should merge it.
> - Continuum needs a non-partioned pom
> - pom processing mevenide's etc.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
