[
http://jira.amdatu.org/jira/browse/AMDATU-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff resolved AMDATU-117.
------------------------------------
Assignee: Marcel Offermans (was: Bram de Kruijff)
Fix Version/s: 0.3.0-M0
Resolution: Fixed
The module amdatu-parent has been split off containing all metadata with it's
own lifecycle. At present under amdatu:amdatu:2:pom
> 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: Build & Release management
> Affects Versions: 0.0.4, 0.3.0-M0
> Environment: all
> Reporter: Bram de Kruijff
> Assignee: Marcel Offermans
> Fix For: 0.3.0-M0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
