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

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

gnodet commented on PR #1638:
URL: https://github.com/apache/maven/pull/1638#issuecomment-2291018175

   > I plan to backport to 3.x and publish it, because there were also some 
other changes being supported meanwhile in Maven 3.x. I don't think this causes 
any harm here. Later on we can remove all outdated elements from the MDO in 
master.
   
   They are part of modello support for history.  We do actually use the same 
MDO in two different versions to generate the v3 and v4 model classes.  I agree 
this is not used for plugins, but I don't see the point of removing those.




> Deprecate o.a.m.plugins.annotations.Component
> ---------------------------------------------
>
>                 Key: MPLUGIN-530
>                 URL: https://issues.apache.org/jira/browse/MPLUGIN-530
>             Project: Maven Plugin Tools
>          Issue Type: Improvement
>          Components: maven-plugin-annotations
>    Affects Versions: 3.13.1, 4.0.0-beta-1
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>              Labels: plugin-descriptor-1.1
>
> The annotation 
> [{{org.apache.maven.plugin.plugins.annotations.Component}}|https://maven.apache.org/plugin-tools/maven-plugin-annotations/apidocs/org/apache/maven/plugins/annotations/Component.html]
>  should be deprecated in favour of [JSR 330 
> annotations|https://maven.apache.org/maven-jsr330.html#how-to-use-jsr-330-in-plugins].
> At the same time the related section of the plugin descriptor 
> https://maven.apache.org/ref/3-LATEST/maven-plugin-api/plugin.html#requirement
>  should be deprecated as well.
> Compare with the discussion in 
> https://lists.apache.org/thread/xfy3wlfxskqw3kmmyj9zxpcj548ft7k8.



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

Reply via email to