maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abel Salgado Romero (JIRA)" <>
Subject [jira] [Commented] (MSITE-849) Unable to inject MavenProject when using `mvn site:run`
Date Sun, 18 Aug 2019 17:13:00 GMT


Abel Salgado Romero commented on MSITE-849:

{quote}I don't think that Doxia should be tied to MavenProject. It can be used and shall be
used w/o Maven.{quote}
There's no other way to add additional configurations to custom converters, so we just rolled
with it.
If it should be in another way, that's definitely a question to the Doxia Leads. Imho it's
a bit too restrictive with what information it makes available to converters.

{quote}If you say that the Asciidoc parser ist not init'ed. Are you sure that this component
is handled properly at all?{quote}
The no initialization is because -I assume- uses some lazy init. And since it works fine with
{{site:site}}, I assume it's correct.

> Unable to inject MavenProject when using `mvn site:run`
> -------------------------------------------------------
>                 Key: MSITE-849
>                 URL:
>             Project: Maven Site Plugin
>          Issue Type: New Feature
>    Affects Versions: 3.7.1, 3.8.2
>            Reporter: Abel Salgado Romero
>            Assignee: Michael Osipov
>            Priority: Major
> In we inject a MavenProject to
obtain addition configurations from the pom.xml (
> This works fine with {{site:site}}, but when using {{site:run}} and accessing one of
the Asciidoc generated pages we get the error below.
> I saw that:
> * The error occurs when trying to retrieve the instance of the MavenProject.
> * Behavior is the same if I directly inject the MavenProject instead of using a provider.
That is, {{site:site}} works, {{site:run}} fails because it cannot find the instance.
> {code:java}
> Problem accessing /hello.html. Reason:
>     Server Error
> Caused by:
> Unable to provision, see the following errors:
> 1) Error in custom provider, Cannot access Key[type=org.apache.maven.project.MavenProject,
annotation=[none]] outside of a scoping block
>   at org.apache.maven.execution.scope.internal.MojoExecutionScopeModule.configure(
(via modules: org.eclipse.sisu.wire.WireModule -> org.apache.maven.execution.scope.internal.MojoExecutionScopeModule)
>   while locating org.apache.maven.project.MavenProject
> 1 error
> 	at
> 	at$1.get(
> 	at
> 	at org.apache.maven.doxia.DefaultDoxia.parse(
> {code}
> * How to reproduce:
> # clone
> # cd asciidoc-maven-site-example
> # mvn site:run
> # Access {{http://localhost:8080/hello.html}}
> * Env:
> {code}
> $ mvn -v
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T21:00:29+02:00)
> Maven home: /home/----/.sdkman/candidates/maven/current
> Java version: 1.8.0_222, vendor: AdoptOpenJDK, runtime: /home/-----/.sdkman/candidates/java/8.0.222.hs-adpt/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.1.21-1-manjaro", arch: "amd64", family: "unix
> {code}

This message was sent by Atlassian JIRA

View raw message