[MNG-6347] Support custom module lifecycle

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Core
• Assignee: Unassigned
• Reporter: Romain Manni-Bucau
• Created: 24/Jan/18 13:38
• Updated: 04/Sep/18 11:56

Description

With front builds wired to maven it starts to be challenging to have a functional lifecycle,
common workaround is to use generate-sources to setup the node environment (install node + npm install), process-sources to enrich it with project specific data (cp myjslib src/main/frontend/node_module), generate-resources to generate the application (npm build) and build-helper-maven-plugin to add the generated folder (src/main/frontend/dist) in META-INF/resources of the produced jar.

This is just a simple example but it can be much more complex and it is harder and harder to insert steps with the limited phases of the default lifecycle. Also the fact you cannot define the same plugin N times (without having a warning) means it is sometimes not possible to have the right execution order.

To solve that it would be nice to have a way to specify the order of the executions or add custom phases in between existing ones directly into the project - without having to do it in a plugin/extension.

Issue Links

• is related to: MNG-5666 Divide lifecycle in prePhases, phases and postPhases
• is related to: MNG-6289 The ability to add a new phase to default lifecycle