[
https://issues.apache.org/jira/browse/MNG-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kanters resolved MNG-6566.
---------------------------------
Fix Version/s: 4.0.0-alpha-1
Resolution: Fixed
Fixed in
[d8c2cc7e4ae8e1c82be49aa264f0a0ae026b1f5a|https://github.com/apache/maven/commit/d8c2cc7e4ae8e1c82be49aa264f0a0ae026b1f5a].
Integration tests in
[7bb6eb02e78c0d9c2a54f1713f5b8e51c11da6d2|https://github.com/apache/maven-integration-testing/commit/7bb6eb02e78c0d9c2a54f1713f5b8e51c11da6d2].
> @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)
