Difference between revisions of "MNG-6189"
Jump to navigation
Jump to search
| Line 75: | Line 75: | ||
</project> | </project> | ||
</source> | </source> | ||
| − | + | === add a reporting node === | |
Then you might want to create a new node '''<reporting></reporting>''' (it it does not exist yet) directly unter the '''<project><project>''' node: | Then you might want to create a new node '''<reporting></reporting>''' (it it does not exist yet) directly unter the '''<project><project>''' node: | ||
<source lang='xml' highlight="2-3"> | <source lang='xml' highlight="2-3"> | ||
| Line 83: | Line 83: | ||
</project> | </project> | ||
</source> | </source> | ||
| + | === cut & paste the list of report plugins === | ||
Now cut&paste the list of report plugins from the configuration above into it like this: | Now cut&paste the list of report plugins from the configuration above into it like this: | ||
<source lang='xml' highlight="2-10"> | <source lang='xml' highlight="2-10"> | ||
| Line 98: | Line 99: | ||
</project> | </project> | ||
</source> | </source> | ||
| + | === remove configuration node if empty === | ||
In the plugins list in the build part only: | In the plugins list in the build part only: | ||
<source lang='xml' highlight="5-8"> | <source lang='xml' highlight="5-8"> | ||
| Line 113: | Line 115: | ||
</project> | </project> | ||
</source> | </source> | ||
| + | === keep configuration node if non empty === | ||
is needed or if you have any non report configurations: | is needed or if you have any non report configurations: | ||
<source lang='xml' highlight="5-11"> | <source lang='xml' highlight="5-11"> | ||
| Line 131: | Line 134: | ||
</project> | </project> | ||
</source> | </source> | ||
| + | == Check result == | ||
| + | run | ||
| + | <source lang='bash'> | ||
| + | mvn site | ||
| + | </source> | ||
| + | to check that the error went away and the site plugin is working as expected. | ||
= Example = | = Example = | ||
See https://github.com/BITPlan/com.bitplan.antlr/blob/master/pom.xml for a complete pom.xml example | See https://github.com/BITPlan/com.bitplan.antlr/blob/master/pom.xml for a complete pom.xml example | ||
Revision as of 16:29, 14 October 2017
As discussed in:
https://stackoverflow.com/questions/46742407/some-problems-were-encountered-while-building-the-effective-model-for when you see the warning:
[WARNING] [WARNING] Some problems were encountered while building the effective model for com.bitplan.antlr:com.bitplan.antlr:jar:0.0.1 [WARNING] Reporting configuration should be done in <reporting> section, not in maven-site-plugin <configuration> as reportPlugins parameter. @ line 213, column 20 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING]
You have run into an issue that is explained in:
What to do?
You get this error if your maven pom.xml configuration looks like this:
original pom.xml
<project>
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.0</version>
<configuration>
<!-- configuration of reports to be included in site -->
<reportPlugins>
<plugin>
<!-- report plugin 1 -->
...
</plugin>
<plugin>
<!-- report plugin 1 -->
...
</plugin>
<reportPlugins>
</configuration>
</plugin>
<plugins>
</build>
</project>
upgrade org.apache.maven.plugins version
You first might want to upgrade your plugin version. You can find the current version at search.maven.org
<project>
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.6</version>
<configuration>
<!-- configuration of reports to be included in site -->
<reportPlugins>
<plugin>
<!-- report plugin 1 -->
...
</plugin>
<plugin>
<!-- report plugin 1 -->
...
</plugin>
<reportPlugins>
</configuration>
</plugin>
<plugins>
</build>
</project>
add a reporting node
Then you might want to create a new node <reporting></reporting> (it it does not exist yet) directly unter the <project><project> node:
<project>
<reporting>
</reporting>
</project>
cut & paste the list of report plugins
Now cut&paste the list of report plugins from the configuration above into it like this:
<project>
<reporting>
<plugin>
<!-- report plugin 1 -->
...
</plugin>
<plugin>
<!-- report plugin 1 -->
...
</plugin>
</reporting>
</project>
remove configuration node if empty
In the plugins list in the build part only:
<project>
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.0</version>
</plugin>
<plugins>
</build>
</project>
keep configuration node if non empty
is needed or if you have any non report configurations:
<project>
<build>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.6</version>
<configuration>
...
</configuration>
</plugin>
<plugins>
</build>
</project>
Check result
run
mvn site
to check that the error went away and the site plugin is working as expected.
Example
See https://github.com/BITPlan/com.bitplan.antlr/blob/master/pom.xml for a complete pom.xml example