Hi Dirk,
Ah...
yes the reporting does not allow extensions...
You can only define an extension in the build area or explicit as extension
<build>
<extensions>
<extension>
<...>
</extension>
</extensions>
</build>
why would you like to define the plugin in the reporting as extension?
Kind regards
Karl Heinz
On 3/17/16 7:57 PM, Dirk Mahler wrote:
Hi Karl Heinz,
the "extensions" element is not supported in the reporting section:
<reporting>
<plugins>
<plugin>
<groupId>com.buschmais.jqassistant.scm</groupId>
<artifactId>jqassistant-maven-plugin</artifactId>
<version>1.1.2</version>
<extensions>true</extensions> <!-- Maven complains about a
Malformed POM at this point -->
<reportSets>
<reportSet>
<reports>
<report>report</report>
</reports>
</reportSet>
</reportSets>
</plugin>
</plugins>
</reporting>
Best regards,
Dirk
------ Originalnachricht ------
Von: "Karl Heinz Marbaise" <[email protected]>
An: "Maven Developers List" <[email protected]>
Gesendet: 17.03.2016 18:43:30
Betreff: Re: MavenReport vs. <extensions>true</extensions>
Hi Dirk,
On 3/16/16 9:03 PM, Dirk Mahler wrote:
Hi,
a project of mine (jQAssistant) provides Maven plugin which includes a
Mojo for creating reports for a Maven site:
@Mojo(name = "report", defaultPhase = LifecyclePhase.SITE)
public class ReportMojo extends AbstractMavenReport {
There seems to be a problem if the Maven plugin is declared as extension
(which sometimes is necessary to avoid classloading problems for a Neo4j
instance acting as singleton in the reactor):
<plugin>
<groupId>com.buschmais.jqassistant.scm</groupId>
<artifactId>jqassistant-maven-plugin</artifactId>
<version>1.1.2</version>
<extensions>true</extensions>
</plugin>
In this case the following warning is rendered:
[WARNING] ignoring
com.buschmais.jqassistant.scm:jqassistant-maven-plugin:1.1.2:report goal
since it is not a report: should be removed from reporting configuration
in POM
Is you plugin configured in the reporting section as well as like above?
Kind regards
Karl Heinz Marbaise
This warning is issued by DefaultMavenReportExecutor after passing the
following line:
boolean isMavenReport = MavenReport.class.isAssignableFrom(
mojoClass );
Is there a way to get around that (Maven 3.3.9)?
Best regards from Dresden
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
