Le dimanche 1 juin 2014 18:53:12 Tony Chemit a écrit : > On Sun, 01 Jun 2014 16:54:54 +0200 > > Hervé BOUTEMY <[email protected]> wrote: > > plexus:components-report is not much used AFAIK, I don't even know what it > > prints :) > > > > I don't know what you expect to write in the report. > > Hum you may have misundertood me. > > I just want to get some plexus components, and do my stuff on it. Plexus > *was* just the way until recently to get components in mojo. ok so adding the current project to plugin dependencies is the way to go: not usual, but it's really what you are requiring, ie inject current project to plugin's classpath for it to access Plexus components declared by current project
and it should work even if current project hasn't been installed yet, since reactor content can be resolved just after compilation step you just need to take care at which phase you'll run your plugin > > > Regarding how to do it, In plexus:components-report and plugin-tools, the > > report is not done by loading Mojos but by reading the generated > > descriptor > > and displaying info. > > No not my point to show stuff about plexus component, just want any instance > of a role. > > What type of information are you expecting to report that requires loading > > classes? > > Everything :) More seriously, I need to call some methods on each components > to get what I want to report. > > The @Component on a Map<String, X> is exaclty what I need, but still can't > find out how to make the mojo also take account of the components of the > maven project. > > Perharps is there is simplier way to do this now with guice ? I thing this > could be the solution. > > > Notice: i'm interested, because plugin-tools could perhaps do something > > similar for complex type parameters > > No problem, let's find a nice solution to do this :) it seems you're not doing at all what I expected, so I doubt this can be reused for plugin-tools any idea on how to dicument complex types parameters in plugin documentation is welcome... Regards, Hervé > > tony. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
