Split project metadata from module/profile concerns through seperate parent pom
-------------------------------------------------------------------------------
Key: AMDATU-117
URL: http://jira.amdatu.org/jira/browse/AMDATU-117
Project: Amdatu
Issue Type: Improvement
Components: Maven setup
Affects Versions: 0.0.4
Environment: all
Reporter: Bram de Kruijff
Assignee: Ivo Ladage - van Doorn
The current root pom is getting big and will get bigger. The typical solution
to keep it manageable used by most projects is to split of a seperate project
pom under pom/pom.xml for project metadata while leaving the infrastructural
concerns like modules and profiles in the root pom. (@see felix, ace, etc). I
think it is a nice convention we should follow.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.amdatu.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
