Hey guys,
thank you for the fast response. I ended up using:
@Inject
protected Provider mavenProjectProvider;
Which works perfectly fine.
Thank you.
2017-02-22 9:12 GMT+02:00 Hervé BOUTEMY :
> IIUC, this feature is available since Maven 3.2.1 (MNG-5530)
>
> Regards,
>
> Hervé
>
> Le mardi 21
IIUC, this feature is available since Maven 3.2.1 (MNG-5530)
Regards,
Hervé
Le mardi 21 février 2017, 22:54:41 CET Igor Fedorenko a écrit :
> MavenProject is injected as a MojoExecutionScope'd component (see
> DefaultBuildPluginManager around line 119). Since old-style Plexus
> components are si
MavenProject is injected as a MojoExecutionScope'd component (see
DefaultBuildPluginManager around line 119). Since old-style Plexus
components are singleton's by default, there is only one
AsciidoctorParser instance which holds the first MavenProject it was
used with for the entire build.
Couple
ie. see line 61 of the maven-plugin-tools annotations reference documentation
http://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/
index.html#Supported_Annotations
Regards,
Hervé
Le mardi 21 février 2017, 19:47:05 CET Robert Scholte a écrit :
> On Tue, 21 Feb 2017 16:16:55 +0100
On Tue, 21 Feb 2017 16:16:55 +0100, Petar Tahchiev
wrote:
Hello guys,
I've recently found out something weird while working with the
asciidoctor
maven plugin.My project has the following structure:
PARENT:
- MODULEA
- MODULEB
- MODULEC
and the asciidoctor team have created this doxia
Hello guys,
I've recently found out something weird while working with the asciidoctor
maven plugin.My project has the following structure:
PARENT:
- MODULEA
- MODULEB
- MODULEC
and the asciidoctor team have created this doxia parser to be able to
render asciidoc content as part of your maven
