-
Type: Improvement
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Epic Link:
-
Tags:
-
Backlog priority:1,000
-
Sprint:DevOps-13, DevOps-14
-
Story Points:2
There is common information which is duplicated each time: repositories, distributionManagement, pluginRepositories, ciManagement, issueManagement, licenses, url, organization.
What about creating a parent POM common to all parent poms of each project ? It would strictly only contain minimal information, specific to Nuxeo and independent of any project.
http://hg.nuxeo.org/parent/pom.xml
Versions shouldn't change very often (that was the problem with nuxeo-ecm) and so artifact would be org.nuxeo:nuxeo-parent:1
We could then use it for parents POMs of public projects : org.nuxeo:nuxeo-ecm, org.nuxeo.tools:nuxeo-tools-parent, org.nuxeo:nuxeo-addons-list, ...
Private projects could have their own super parent POM which inherits this one and overwrite some informations (licenses, ...).
For example, Apache use this one: http://svn.apache.org/viewvc/maven/pom/tags/apache-6/pom.xml?view=markup
- is required by
-
JAVACLIENT-100 POM must follow Nuxeo rules and conventions
- Resolved