[MAGNOLIA-2345] Refactor pom files Created: 01/Sep/08  Updated: 23/Jan/13  Resolved: 08/Sep/08

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: None
Fix Version/s: 3.6.2, 3.6.3

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

We currently have one single parent pom, but all modules still extend the magnolia-project parent pom. We need an intermediate parent pom for "external" modules (i.e not the modules included in the reactor build of the main Magnolia project, but those with an independent lifecycle)



 Comments   
Comment by Magnolia International [ 01/Sep/08 ]

There is currently (2008-09-01) a dependency that would prevent releasing all the parent poms at once: the module-community and enterprise parent pom make use of our custom maven plugins; these maven plugins themselve also have a parent pom. To have consistent releases, we'd need to release the main parent and plugins parent, followed by the plugins, then followed by the module-community and enterprise parents.
This will probably lead to some more restructuring of svn (/build)...

Comment by Magnolia International [ 01/Sep/08 ]

todo : check MAGNOLIA-1110 and MAGNOLIA-1439 - fix or close appropriately.

Comment by Magnolia International [ 03/Sep/08 ]

Split of magnolia-parent-pom and parent pom for plugin VS other parent poms: done.

Comment by Magnolia International [ 08/Sep/08 ]

done !
released all parent poms as version 5, along all our maven plugins/tools.

Generated at Mon Feb 12 03:35:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.