[ http://jira.codehaus.org/browse/MNG-2350?page=comments#action_66903 ]
Gunther Popp commented on MNG-2350: ----------------------------------- I moved the site plugin from <reporting>/<plugins> to <build>/<plugins> and now it works as expected. However, the example in the guide (http://maven.apache.org/plugins/maven-site-plugin/howto.html) places the plugin explicitly in the <reporting>/<plugins> section of the pom. This should be changed, IMO. And please note that the site-plugin works perfectly when it is configured in the <reporting> section (e.g. changing the outputEncoding works fine). Only the <version> tag is ignored in this case. IMO, Maven should report an error or at least a warning when the site-plugin is placed in the wrong section of the POM. > <version> tag is ignored for plugins in the <reporting> section of the POM > -------------------------------------------------------------------------- > > Key: MNG-2350 > URL: http://jira.codehaus.org/browse/MNG-2350 > Project: Maven 2 > Type: Bug > Components: Sites & Reporting > Versions: 2.0.4 > Environment: Windows XP > Reporter: Gunther Popp > > > A version defined for a plugin in the <reporting> section of the POM is > ignored. For example, I would expect that the following definition in a POM > forces the usage of version 2.0-beta-4 of the site-plugin: > <project> > ... > <reporting> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-site-plugin</artifactId> > <version>2.0-beta-4</version> > </plugin> > ... > However, Maven always uses the newer version 2.0-beta-5: > >mvn site -X > + Error stacktraces are turned on. > Maven version: 2.0.4 > ... > [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for > updates from central > [DEBUG] maven-site-plugin: resolved to version 2.0-beta-5 from repository > central > [DEBUG] Trying repository central > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-5/maven-site-plugin-2.0-beta-5.pom > 2/2K > 2K downloaded > [DEBUG] Artifact resolved > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for > project: null:maven-site-plugin:maven-plugin:2.0-beta-5 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: > org.apache.maven.plugins:maven-plugins:pom:1 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: > org.apache.maven:maven-parent:pom:1 from the repository. > [DEBUG] Trying repository central > Downloading: > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-5/maven-site-plugin-2.0-beta-5.jar > 52K downloaded > [DEBUG] Artifact resolved > ... > It doesn´t matter, if the plugin already exists in the local repostitory or > not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
