[
https://issues.apache.org/jira/browse/MPLUGIN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPLUGIN-323.
----------------------------------
Fix Version/s: (was: 3.7.0)
Assignee: Robert Scholte
Resolution: Won't Fix
@Named/@Inject mechanism is supported since Maven 3.1.0, see [MNG-5382
IT|https://github.com/apache/maven-integration-testing/tree/master/core-it-suite/src/test/resources/mng-5382/src/main/java/org/apache/maven/plugins]
The Plexus Plugin Annotations have the same state as @Autowired/@Bean for
Spring Framework: they still work, but one should prefer javax.inject.
Replacing annotations will only cause confusion on the web, so let's leave it
as it is.
> 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: Herve Boutemy
> Assignee: Robert Scholte
> Priority: Major
>
> 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
(v8.20.1#820001)
