[BUILD-148] Merge build-tools with poms lifecycle Created: 05/Aug/14  Updated: 13/Apr/17  Resolved: 23/Oct/14

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: Build Resources 1.6, Site Skin 1.3, Maven Assemblies 1.3, SetProperty Maven plugin 1.2, Magnolia Bundle Maven Plugin 1.1, POMs 30

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

Issue Links:
dependency
is depended upon by BUILD-182 Review/remove our Maven plugins Accepted
duplicate
duplicates BUILD-29 Merge/refactor/remove maven-plugins a... Closed
Template:
Acceptance criteria:
Empty
Release notes required:
Yes

 Description   

The plugins and the "tools" currently have completely independent lifecycles. Getting rid of the plugins would simplify our build for parent poms. We currently have a semi-circular dependency that forces to build and release, in this order:

  • "super" parent pom
  • plugins / tools
  • "concrete" parent poms that configure the above plugins.
    The "tools" are merely files which we bundle in a jar which we use to further configure parent poms. Those could IMO follow the same lifecycle and versioning as the parent poms do.

Resolution:
The different parts of our build projects have been migrated to Git and merged into a single reactor project. However, they still have different lifecycles (i.e plugins don't need to be released with every version of the poms)
We might further change this with BUILD-182. Meanwhile, the build is using the -pl, -am and -amd flags of Maven. See README.txt for details.



 Comments   
Comment by Magnolia International [ 12/Sep/14 ]

Did some tests with mvn -pl and it looks like we could possibly have all parent poms and maven plugins in a single reactor, selectively releasing only the bits we need.
There are some issues to workaround http://jira.codehaus.org/browse/MRELEASE-767
As for the above, indeed some of our plugins could be dropped and replaced by maven configuration, but some might still be useful and/or less verbosely configured.

Generated at Sun Feb 11 23:39:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.