[
https://jira.codehaus.org/browse/MPLUGIN-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPLUGIN-225:
----------------------------------
Description:
Just like {{MavenProject}} it is possible to define the {{MojoExecution}} as:
{code}
@Component
private MojoExecution mojoExecution ;
{code}
but actually generated descriptor works only for Maven 3, not for Maven 2
was:
Just like {{MavenProject}} it should be possible to define the
{{MojoExecution}} as:
{code}
@Component
private MojoExecution mojoExecution ;
{code}
Fix Version/s: 3.1.1
Summary: Make MojoExecution available as Component compatible with
Maven 2 (was: Make MojoExecution available as Component)
fixed in [r1405318|http://svn.apache.org/viewvc?rev=1405318&view=rev]
generated default value was ${mojo}, which is [only recognized by Maven
3|http://maven.apache.org/ref/3.1-SNAPSHOT/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html]
replaced by ${mojoExecution}, which is recognized by Maven 2 too
> Make MojoExecution available as Component compatible with Maven 2
> -----------------------------------------------------------------
>
> Key: MPLUGIN-225
> URL: https://jira.codehaus.org/browse/MPLUGIN-225
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-annotations
> Affects Versions: 3.1
> Reporter: Robert Scholte
> Assignee: Herve Boutemy
> Priority: Minor
> Fix For: 3.1.1
>
>
> Just like {{MavenProject}} it is possible to define the {{MojoExecution}} as:
> {code}
> @Component
> private MojoExecution mojoExecution ;
> {code}
> but actually generated descriptor works only for Maven 3, not for Maven 2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
