You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2013/07/20 22:59:05 UTC

[jira] (MPLUGIN-204) recognize classical Maven objects as components

     [ https://jira.codehaus.org/browse/MPLUGIN-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy updated MPLUGIN-204:
----------------------------------

    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|http://markmail.org/message/fruuocvtrhmkbo3y], having them automatically injected with @component annotation, recognized by their type, would simplify code

  was:
${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|http://markmail.org/message/fruuocvtrhmkbo3y], having them automatically injected with @component annotation, recognized by their type, would simplify code

    
> recognize classical Maven objects as components
> -----------------------------------------------
>
>                 Key: MPLUGIN-204
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-204
>             Project: Maven 2.x Plugin Tools
>          Issue Type: New Feature
>    Affects Versions: 2.9
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>             Fix For: 3.0
>
>
> $\{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|http://markmail.org/message/fruuocvtrhmkbo3y], having them automatically injected with @component annotation, recognized by their type, would simplify code

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira