You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/12/15 10:16:00 UTC

[jira] [Commented] (MNG-6566) @Execute should not re-execute goals

    [ https://issues.apache.org/jira/browse/MNG-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249612#comment-17249612 ] 

Hudson commented on MNG-6566:
-----------------------------

Build succeeded in Jenkins: Maven » Maven TLP » maven » master #69

See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/69/

> @Execute should not re-execute goals
> ------------------------------------
>
>                 Key: MNG-6566
>                 URL: https://issues.apache.org/jira/browse/MNG-6566
>             Project: Maven
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>            Reporter: Robert Scholte
>            Assignee: Martin Kanters
>            Priority: Major
>             Fix For: 4.0.0-alpha-1
>
>
> We're getting quite a lot of requests for <goal>-no-fork goals, because now often plugins are executed twice because of retriggering plugins due to the @Execute -annotation.
> Maven should be able to discover if there's a need to re-execute those goals/lifecycles.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)