[MPLUGIN-257] deprecate classical Maven objects as components

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2
• Fix Version/s: 3.3
• Assignee: Herve Boutemy
• Reporter: Herve Boutemy
• Created: 06/Feb/14 15:38
• Updated: 16/Jul/14 09:44
• Resolved: 27/Apr/14 10:01

Description

such component annotations added in MPLUGIN-204 were a bad idea, because they cause confusion with Plexus components

it's better to remove the feature and add examples in documentation:

@Parameter( defaultValue="${session}", readonly=true )
private MavenSession session;

@Parameter( defaultValue="${project}", readonly=true )
private MavenProject project;

@Parameter( defaultValue="${mojo}", readonly=true )
private MojoExecution mojo;

@Parameter( defaultValue="${plugin}", readonly=true )
private PluginDescriptor plugin;

@Parameter( defaultValue="${settings}", readonly=true )
private Settings settings;

Issue Links

• relates to: MPLUGIN-266 Incorrect warning comment about deprecated @component usage for maven objects
• relates to: MPLUGIN-270 Deprecation of classical Maven objects as components is broken when using Javadoc tags
• supercedes: MPLUGIN-204 recognize classical Maven objects as components