[
http://jira.codehaus.org/browse/MPIR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222441#action_222441
]
Steve Gilbert commented on MPIR-195:
------------------------------------
I am not missing what you all are saying. I understand completely but I
disagree with the policy.
The analogy about an application that needs Java 6 to run doesn't hold for this
situation. Here is a more accurate analogy: I install a web browser and I
expect that it will be able to render JPEG images on a web page, but it turns
out the version of the graphics renderer the application uses is not specified
and the one it chooses to use out of the box causes it to throw an exception
and crash. It's then on me to change the configuration so that a working
version of the graphics render is used. This makes no sense to me. An
application should perform its core task out of the box without requiring the
user to configure it.
This case is the same. Maven provides the site plugin out of the box through
"mvn site". The site plugin by default uses the project info reports plugin.
I don't have to configure either one of these plugins into maven. They are
there out of the box. I don't think it's unreasonable to have an expectation
that the application be configured out of the box to use the correct
combination of these plugins. If Maven did not compile java code out of the
box without setting a plugin version first would that be a bug?
I realize you all disagree and believe that expectation is not reasonable. I
also realize you are not going to change your opinion about that. I am going
to change my poms because I have no other choice at this point. I do
appreciate your attention to and engagement on this issue. I have learned that
my assumption that Maven's core functionality will work out of the box without
additional configuration was a poor one and I have adjusted that expectation.
> 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
