[MPLUGIN-204] recognize classical Maven objects as components

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 3.0
• Assignee: Herve Boutemy
• Reporter: Herve Boutemy
• Created: 27/May/12 14:09
• Updated: 06/Nov/23 07:15
• Resolved: 27/May/12 15:22

Description

${session}, ${project}, ${mojo}, ${plugin}, ${settings} expressions are classical Maven objects injected into Mojos with readonly attribute (ie not configurable)

As discussed on the dev list, having them automatically injected with @component annotation, recognized by their type, would simplify code

Issue Links

• is related to: MNG-5695 inconsistent custom Guice scope bindings
• is related to: MPLUGIN-225 Make MojoExecution available as Component compatible with Maven 2
• is superceded by: MPLUGIN-257 deprecate classical Maven objects as components
• relates to: MPLUGIN-214 generated descriptor for Maven object components is not like previous versions
• relates to: MPLUGIN-241 Add Annotation for Objects injected by Maven
• relates to: MPLUGIN-249 give snippets to show use of expressions to get Maven objects