On 28 May 2012 08:11, Hervé BOUTEMY <[email protected]> wrote: > We can implement @component based on field type *and name*: > > // defaults to ${project} > @Component > MavenProject myProject > > // but reactorProjects gives ${reactorProject} > @Component > MavenProject reactorProjects
Should be an array or list ^^^ is ending with a "s" > > > And the list of magical field type+name can grow as much as we find use cases. > > But is this a good idea? Isn't it too magical? > > Regards, > > Hervé > > Le dimanche 27 mai 2012 22:21:46 Hervé BOUTEMY a écrit : >> Le samedi 26 mai 2012 22:06:47 Brett Porter a écrit : >> > // inject stuff for Maven - session covers all but should also support >> > >> > the same for project, localRepository, reactorProjects, // mojoExecution, >> > executedProject, plugin, settings >> > >> > @Inject >> > private MavenSession session; >> >> I just implemented project, mojo, plugin, session and settings: see >> MPLUGIN-204 [1] >> I didn't implement localRepository, reactorProjects, executedProject: we >> can't differentiate executedProject from project based on its simple class >> name, and I hesitated for localRepository and reactorprojects: is the type >> sufficient? >> >> Adding new magical Maven objects just requires adding config in PluginUtils. >> >> Regards, >> >> Hervé >> >> [1] http://jira.codehaus.org/browse/MPLUGIN-204 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
