[
https://issues.apache.org/jira/browse/MPLUGIN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483529#comment-16483529
]
Robert Scholte commented on MPLUGIN-323:
----------------------------------------
Let's keep https://wiki.eclipse.org/Sisu/PlexusMigration in mind. To me
@Component to @Requirement is like @Named to @Inject ,so I'm not sure if this
would be an improvement.
> create @Requirement annotation to replace @Component (should be deprecated)
> ---------------------------------------------------------------------------
>
> Key: MPLUGIN-323
> URL: https://issues.apache.org/jira/browse/MPLUGIN-323
> Project: Maven Plugin Tools
> Issue Type: Wish
> Components: maven-plugin-annotations, maven-plugin-tools-javadoc
> Affects Versions: 3.5
> Reporter: Hervé Boutemy
> Priority: Major
> Fix For: 3.6
>
>
> injecting a Plexus component into a mojo is currently marked through
> {{@Component}} annotation (or {{@component}} javadoc tag)
> This "component" term is misleading for 2 reasons:
> 1. in plugin descriptor, it creates a {{<requirement>}} XML element:
> http://maven.apache.org/ref/3-LATEST/maven-plugin-api/plugin.html#class_requirement
> 2. in Plexus, injecting is marked with {{@Requirement}} annotation, when
> {{@Component}} is used to define a component:
> http://codehaus-plexus.github.io/plexus-containers/plexus-component-annotations/
> This annotation creates great confusion for years, then even if Plexus is
> being dropped for javax.inject, fixing this misleading terms would be
> beneficial IMHO
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
