[
http://jira.codehaus.org/browse/MPIR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MPIR-195.
------------------------------
Resolution: Not A Bug
There is no "default" version of the pir-plugin. It is not specified in any
version of the maven super pom, so maven will use the last version it finds in
your repo. OTOH, the site plugin version is specified in the super pom, so
there is a "default" version, but it depends on which maven version you are
running. In brief, your build is not reproducible (the fact that it works for
you does not imply that it will also work for me), that's why you should always
specify explicitly the versions of all plugins you are using [1]. This is all
standard maven philosophy, if you have any questions about it please read up on
the docs (admittedly often hard to find), or discuss it on the mailing list.
Finally, it has been specifically emphasized in the release notes that pir-2.2
requires site plugin 2.1. This is not a bug.
[1] http://maven.apache.org/guides/mini/guide-configuring-plugins.html
> Attempting to configure maven-project-info-reports-plugin in reporting
> section of pom causes java.lang.ArrayIndexOutOfBoundsException to be thrown
> by site goal
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MPIR-195
> URL: http://jira.codehaus.org/browse/MPIR-195
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Steve Gilbert
> Assignee: Lukas Theussl
> Priority: Critical
>
> With an empty local repository using Maven 2.2.1, if plugin is added to the
> reporting section of the pom.xml, the site goal throws a
> java.lang.ArrayIndexOutOfBoundsException and the build fails.
> Removing the plugin from the section or changing the version back to 2.1.2
> (from 2.2) resolves the problem.
> This prevents using any configuration of the plugin.
> Placing the following pom into an empty directory and executing "mvn site"
> demonstrates the bug.
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> <modelVersion>4.0.0</modelVersion>
> <groupId>testgroup</groupId>
> <artifactId>testart</artifactId>
> <packaging>jar</packaging>
> <version>1.0-SNAPSHOT</version>
> <reporting>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-project-info-reports-plugin</artifactId>
> <version>2.2</version>
> </plugin>
> </plugins>
> </reporting>
> </project>
> {code}
--
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
