[jira] [Commented] (MPLUGIN-378) Detect legacy/javadoc Mojo definitions, warn to use Java 5 annotations

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on MPLUGIN-378:
----------------------------------------

gnodet commented on PR #46:
URL: https://github.com/apache/maven-plugin-tools/pull/46#issuecomment-1274942334

   @slachiewicz @slawekjaranowski @cstamas so what's the status of this PR ? I've merged master, but should that be integrated into the upcoming 3.7.0 release or delayed ?




> Detect legacy/javadoc Mojo definitions, warn to use Java 5 annotations
> ----------------------------------------------------------------------
>
>                 Key: MPLUGIN-378
>                 URL: https://issues.apache.org/jira/browse/MPLUGIN-378
>             Project: Maven Plugin Tools
>          Issue Type: Task
>          Components: maven-plugin-tools-javadoc
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 3.7.0
>
>
> In short: deprecate java-javadoc mojo descriptor extractor, as everyone should use the newer Java5 annotation based Mojo Annotations instead. Make the plugin warn (later fail?) during build if the built sources contain mojo definitions defined using javadoc qdox tags.
> This change will have some incompatible on extractor API, hence the 3.7.0 version.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)