Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Fri, 15 Jul 2016 12:21:20 +0000 (UTC)
From: =?utf-8?Q?J=C3=B6rg_Sesterhenn_=28JIRA=29?= <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12796350.1406283725000.40954.1468585280670@Atlassian.JIRA>
In-Reply-To: <JIRA.12796350.1406283725000@Atlassian.JIRA>
References: <JIRA.12796350.1406283725000@Atlassian.JIRA> <JIRA.12796350.1406283725318@arcas>
Subject: [jira] [Commented] (MNG-5666) Divide build in pre-build, build and
 post-build
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 15 Jul 2016 12:21:22 -0000


    [ https://issues.apache.org/jira/browse/MNG-5666?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D153793=
09#comment-15379309 ]=20

J=C3=B6rg Sesterhenn commented on MNG-5666:
--------------------------------------

Thanks for the update!

> Divide build in pre-build, build and post-build
> -----------------------------------------------
>
>                 Key: MNG-5666
>                 URL: https://issues.apache.org/jira/browse/MNG-5666
>             Project: Maven
>          Issue Type: Sub-task
>          Components: FDPFC, Plugins and Lifecycle
>            Reporter: Robert Scholte
>            Assignee: Jason van Zyl
>             Fix For: 3.x / Backlog
>
>
> Original proposal
> {quote}
> PROPOSAL 1: PerProject and PerPhase Executions
> =20
> I've recently introduced the installAtEnd/deployAtEnd as an experimental =
feature which should improve the behavior of Maven without having to wait f=
or the implementation in Maven Core, which would have a huge impact.
> The reason is that you only want to install and/or deploy only after all =
modules have been build and verified successfully.
> This feature works for most projects, however there are cases which canno=
t be solved by the plugin solution and require a change in the handling of =
lifecycles in Maven Core.
> Up unto the verify-phase you want to execute all phases per project, wher=
eas the install and deploy should be executed per phase.
> Consider a root project with 2 modules, these should be executed like thi=
s
> =20
> root   : validate ... verify
> module1: validate ... verify
> module2: validate ... verify
> root   : install
> module1: install
> module2: install
> root   : deploy
> module1: deploy
> module2: deploy
> {quote}
> After one of the google hangout session we came up with the following ide=
a: divide the build in pre-build, build and post-build
> First the {{pre-build}} would do a validate of the whole project.
> The {{build}} runs from {{initialize}} up to {{verify}}
> The {{post-build}} would handle the distribution, being {{install}}/{{dep=
loy}}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)