You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2018/01/24 13:39:00 UTC

[jira] [Created] (MNG-6347) Support custom module lifecycle

Romain Manni-Bucau created MNG-6347:
---------------------------------------

             Summary: Support custom module lifecycle
                 Key: MNG-6347
                 URL: https://issues.apache.org/jira/browse/MNG-6347
             Project: Maven
          Issue Type: New Feature
          Components: core
            Reporter: Romain Manni-Bucau


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 produces 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 can 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)