Choosing dependency resolution dynamically?

I've got a plugin destined for PROCESS_CLASSES. Normally, it will look only at the compile classpath. But I would like to add a scope parameter to optionally look at the test classpath. Is there some alternative to the @Mojo parameters to allow me to request test dependency resolution? ---

I thought that @Component was a good thing

[WARNING] Deprecated @component for project field in com.fasterxml.jackson.jsonschemaplugin.JsonSchemaMojo.: replace with @parameter name="${project}" @readonly This surprised me, coming from the maven-plugin-plugin when used as a report. --

To plexus-component or not to plexus-component ...

I'm working on a plugin where there's a use-case in which the user will want to add something to the plugin's classpath and then configure a class. Is there any advantage to using plexus injection for this as opposed to just ordinary classpath fishing for a named class? --

Re: Integrate Maven Site reporting with maven plugin that externally create report html page.

Thx @Herve BOUTEMY for answer, but when I override isExternal() to return true nothing changes.. The same report generation is invoked after executing 'mvn site'. I spent hours and couldn't find, but may be is it possible to reference concrete report link in site reporting section? e.g. '${project}

Re: I thought that @Component was a good thing

We made a small mistake by exposing common Objects such as MavenProject, MavenSession and Settings as Components to make it easier to inject them. However, these kind of of Objects are not injected like a (Plexus)-Component, hence the reason why we reverted this feature. Robert Op Tue, 02 De

Re: I thought that @Component was a good thing

But these are 'maven' @Component, not plexus @Component, rigtht? Two different annotation classes? You've regretted the entire maven-not-plexus @Component? On Tue, Dec 2, 2014 at 2:16 PM, Robert Scholte wrote: > We made a small mistake by exposing common Objects such as MavenProject, > MavenSessi

Re: To plexus-component or not to plexus-component ...

I think it largely depends on if you want service injection or not. If your "component" requires other services it might make sense to make it plexus-managed. As an example, I have been irritated the the plexus-io collections are themselves plexus-components. This is because they get the plexus lo

Re: I thought that @Component was a good thing

A Mojo @Component annotated field should match a Plexus @Component annotated class. Op Tue, 02 Dec 2014 20:18:26 +0100 schreef Benson Margulies : But these are 'maven' @Component, not plexus @Component, rigtht? Two different annotation classes? You've regretted the entire maven-not-plexu

Re: I thought that @Component was a good thing

here is the Jira issue: http://jira.codehaus.org/browse/MPLUGIN-257 Regards, Hervé Le mardi 2 décembre 2014 20:16:52 Robert Scholte a écrit : > We made a small mistake by exposing common Objects such as MavenProject, > MavenSession and Settings as Components to make it easier to inject them. > H

Re: Integrate Maven Site reporting with maven plugin that externally create report html page.

there was a misunderstanding: when isExternal() returns true, there is no Doxia generation, but Report.generate() is called you should call the generation engine from generate(): IIUC, you're calling the generation engine from another point, and that's the problem Regards, Hervé Le mardi 2 dé

Re: Integrate Maven Site reporting with maven plugin that externally create report html page.

Yes that't true and I get my report being generated. But after that I would like to embed link to my externally created report in site reporting section.. So firstly I execute 'mvn site'. Because I declared my plugin in reporting section my Mojo that extends AbstractMavenReport is invoked and crea