[
http://jira.codehaus.org/browse/MPIR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222365#action_222365
]
Dennis Lundberg commented on MPIR-195:
--------------------------------------
Steve,
I think you are missing the point that Lukas is trying to make.
PIR Plugin 2.2 requires at least version 2.1 of the Site Plugin to work
correctly. Unfortunately it is not possible for a plugin so say (in a
programmatic way) that it requires a certain version of another plugin. What
has been done instead is to document this requirement as much as possible,
including mentioning it in the announcement.
An analogy would be that you were trying to use a new piece of software that
requires Java 6, but you are trying it on Java 5. Do you consider that to be a
bug in the software?
Your failure to follow the best practice that Lukas mentions, about always
specifying your plugin versions, is the reason why you are having this problem
now. Your builds will always be breakable if a new version comes out if you
don't specify them. It usually takes an incident like this for people to start
thinking some more about this.
> 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
