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
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
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
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
[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.
--
