You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/03/24 21:09:00 UTC

[jira] [Closed] (MNG-6289) The ability to add a new phase to default lifecycle

     [ https://issues.apache.org/jira/browse/MNG-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MNG-6289.
-------------------------------
       Resolution: Incomplete
    Fix Version/s:     (was: waiting-for-feedback)

No reaction for six months.

> The ability to add a new phase to default lifecycle
> ---------------------------------------------------
>
>                 Key: MNG-6289
>                 URL: https://issues.apache.org/jira/browse/MNG-6289
>             Project: Maven
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.5.0
>            Reporter: Rami Ojares
>            Priority: Major
>
> 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.



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