[MNG-6289] The ability to add a new phase to default lifecycle

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 3.5.0
• Component/s: Core
• Assignee: Unassigned
• Reporter: Rami Ojares
• Created: 28/Sep/17 11:52
• Updated: 24/Mar/18 21:08
• Resolved: 24/Mar/18 21:08

Description

At the moment there is no way to add a phase to the default lifecycle.
The best one can do is to create a new lifecycle with one or more phases.
Then a phase can be bound to a goal.
And in the Mojo that implements the goal one can fork the default lifecycle's phase say install or deploy.
But the default lifecycle is always executed forked.
This means that the information that the package phase adds to the maven project for example about the attached artifacts is lost because it is executed forked.

The simplest way to remedy this situation would be to add possibility in the @Execute annotation to run a phase not-forked.
Eg. @Execute (phase = LifecyclePhase.INSTALL, forked = false)
This way I could create a new lifecycle but run the default lifecycle first as a requirement within the same MavenProject.

Issue Links

• relates to: MNG-6347 Support custom module lifecycle