ok, now I understand where we diverge yes, "normal" plugin-tools @Component are translated into Plexus requirements
but actual plugin-tools @Component support for Maven objects is a hack that translates into parameter, not into requirement [1] so this hack is confusing when this hack will be removed, real @Component translated to Plexus requirements will be possible: for the moment, the hack makes such thing impossible Regards, Hervé [1] http://svn.apache.org/viewvc/maven/plugin-tools/trunk/maven-plugin-tools-annotations/src/main/java/org/apache/maven/tools/plugin/annotations/JavaAnnotationsMojoDescriptorExtractor.java?r1=1341650&r2=1343086&pathrev=1343086&diff_format=h Le samedi 8 février 2014 11:00:48 Igor Fedorenko a écrit : > On 2/8/2014, 9:56, Hervé BOUTEMY wrote: > > ok, here the confusion is that there are 2 @Component annotations: > > org.apache.maven.plugins.annotations.Component = plugin-tools > > and > > org.codehaus.plexus.component.annotations.Component = Plexus on Guice > > > > plugin-tools @Component annotation for objects injected by > > PluginParameterExpressionEvaluator causes confusion at plugin-tools level > > Can you point me at the code that implements this? I was under > impression that plugin-tools @Component was translated to plexus/guice > requirement at runtime and there was no real difference between the two. > Any special handing of @Component in PluginParameterExpressionEvaluator > should not be necessary in 3.2 and I would like to clean this up. > > -- > Regards, > Igor > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
