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. 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. What type of information are you expecting to report that requires loading classes? Notice: i'm interested, because plugin-tools could perhaps do something similar for complex type parameters Regards, Hervé Le dimanche 1 juin 2014 09:46:20 Tony Chemit a écrit : > On Sat, 31 May 2014 14:22:13 +0200 > > Hervé BOUTEMY <[email protected]> wrote: > > Le samedi 31 mai 2014 13:55:47 Hervé BOUTEMY a écrit : > > > logical, finally: why would the plugin classpath contain actual project? > > > > > > And since resolution happens from workspace, I imagine that the plugin > > > can > > > get classes just after compile phase, isn't it? > > > > s/workspace/reactor/ > > So for you, this is the good way to do it ? > > I would not mind to create a new lookup realm for plexus container to > include the module target/classes. > > I tried this but it did not work either. I would just need a little help on > this code. > > If someone could point me where to look, ... > > I would really that the report do his internal cooking instead of adding > configuration in the pom.xml. > > thanks, > > tony. > > > > Regards, > > > > > > Hervé > > > > > > Le samedi 31 mai 2014 12:46:34 Tony Chemit a écrit : > > > > On Sat, 31 May 2014 11:19:57 +0200 > > > > > > > > Hervé BOUTEMY <[email protected]> wrote: > > > > > you mean you're trying to do something like plexus:components-report > > > > > [1]? > > > > > > > > Yes > > > > > > > > > are you sure you generated the plexus descriptor before running the > > > > > mojo > > > > > injecting implementations? > > > > > > > > Yes, > > > > > > > > project/target/classes/META-INF/plexus/components.xml is there. > > > > > > > > The maven plugin is here: > > > > > > > > http://svn.nuiton.org/eugene/trunk/eugene-maven-plugin/src/main/java/o > > > > rg/n > > > > ui ton/eugene/plugin/AbstractEugeneReport.java > > > > http://svn.nuiton.org/eugene/trunk/eugene-maven-plugin/src/main/java/o > > > > rg/n > > > > u > > > > iton/eugene/plugin/TagValueReport.java > > > > > > > > I managed to use it adding this configuration in the pluginManagement > > > > > > > > <plugin> > > > > > > > > <groupId>org.nuiton.eugene</groupId> > > > > <artifactId>eugene-maven-plugin</artifactId> > > > > <dependencies> > > > > > > > > <dependency> > > > > > > > > <groupId>${project.groupId}</groupId> > > > > <artifactId>${project.artifactId}</artifactId> > > > > <version>${project.version}</version> > > > > > > > > </dependency> > > > > > > > > </dependencies> > > > > > > > > </plugin> > > > > > > > > but it look a bit strange to do this, plus it won't work if the > > > > project > > > > was > > > > never built... > > > > > > > > > Regards, > > > > > > > > > > Hervé > > > > > > > > > > [1] > > > > > http://plexus.codehaus.org/plexus-maven-plugin/components-report-moj > > > > > o.ht > > > > > m > > > > > l> > > > > > > > > > > Le samedi 31 mai 2014 10:05:06 Tony Chemit a écrit : > > > > > > Hi, > > > > > > > > > > > > Let me explain my problem, hopes to find here a solution about it. > > > > > > > > > > > > I am currently writing a maven report to describe some plexus > > > > > > components. > > > > > > > > > > > > The idea is to be able to describe the components declared in the > > > > > > very > > > > > > same > > > > > > maven module. > > > > > > > > > > > > I tried this, it found components of the same role from the > > > > > > dependencies, > > > > > > but not the one declared in the module : > > > > > > > > > > > > @org.apache.maven.plugins.annotations.Component(role = > > > > > > TagValueDefinitionProvider.class) protected Map<String, > > > > > > TagValueDefinitionProvider> tagValueProviders; > > > > > > > > > > > > What did I miss ? > > > > > > > > > > > > Thanks for any help. > > > > > > > > > > > > tony. > > > > > > > > > > -------------------------------------------------------------------- > > > > > - > > > > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
