[
http://jira.amdatu.org/jira/browse/AMDATU-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff resolved AMDATU-117.
------------------------------------
Resolution: Won't Fix
It turns out that there is no good way to do this in Maven 2 without getting
into trouble with site generation and release management. The former gets
confused when parent hierarchie does not match directory structure while the
latter requires the parent to be released before one can release the project
which would required seperate release management on the parent. Although
working around this this probably could be done it would require heaps of
configuration that I feel is not worth it at this point as we are still going
to restructure the layout and plan on moving to Maven 3 which will add support
for splitting through mixins in the future. Finally note that xsinclude is no
option either as the Maven parser does not support it.
> 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: Bram de Kruijff
> Fix For: 0.0.6
>
>
> 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
