You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/08/07 13:36:00 UTC

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

     [ https://issues.apache.org/jira/browse/MPLUGIN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MPLUGIN-378:
-----------------------------------
    Summary: Detect legacy/javadoc Mojo definitions, warn to use Java 5 annotations  (was: Detect legacy/javadoc Mojo definitions, warn to use Java5 annotations)

> 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: Tamás Cservenák
>            Assignee: Tamás Cservenák
>            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)