[ https://issues.apache.org/jira/browse/MPLUGIN-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630885#comment-17630885 ]
Hudson commented on MPLUGIN-439: -------------------------------- Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-tools » master #82 See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-tools/job/master/82/ > 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 > Assignee: Konrad Windszus > Priority: Major > Fix For: next-release > > > 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)