[
https://issues.apache.org/jira/browse/MPLUGIN-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627123#comment-17627123
]
Konrad Windszus commented on MPLUGIN-439:
-----------------------------------------
[~gnodet] The same is true for the Maven 4 API at
https://github.com/apache/maven/blob/1ada7a590237db7f6f7eaa98180dd5a402412490/api/maven-api-core/src/main/java/org/apache/maven/api/plugin/annotations/Execute.java#L47.
> Execute annotation only supports standard lifecycle phases due to use of enum
> -----------------------------------------------------------------------------
>
> Key: MPLUGIN-439
> URL: https://issues.apache.org/jira/browse/MPLUGIN-439
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: maven-plugin-annotations
> Reporter: Konrad Windszus
> Priority: Major
>
> The {{Execute}} annotation defined at
> https://github.com/apache/maven-plugin-tools/blob/6dfbd4b6e2674b81702d3417e57b471afad40535/maven-plugin-annotations/src/main/java/org/apache/maven/plugins/annotations/Execute.java#L45
> only supports one of the predefined phases from
> https://github.com/apache/maven-plugin-tools/blob/master/maven-plugin-annotations/src/main/java/org/apache/maven/plugins/annotations/LifecyclePhase.java.
> That can't be used for custom lifecycle ids, though.
> There should be another element on that annotation which should allow to use
> custom ids (as regular String values).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
