[
http://jira.codehaus.org/browse/MPIR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222390#action_222390
]
Lukas Theussl commented on MPIR-195:
------------------------------------
bq. Whatever it pulls down is the default version.
But this default version (as you define it) depends on your default repository
and settings (if I happen to have an old version of pir in my local repo, maven
will use that; if you start with an empty repo, maven will use the latest
version it finds in whatever remote repos you have specified), and whenever we
release a new version, maven will give you a new "default". So your build is
not reproducible and you shouldn't be surprised if it breaks at one point.
bq. The fact that it is not declared in a pom does not mean there is no default
version.
Yes it does. What is not in your pom is not defined.
bq. I still assert this is a regression bug.
No it isn't.
bq. We've not declared our site plugin version so that we use the latest
version released by your team. I believe what you are saying is that in fact
that practice is bad and that we should be tied to a specific version and
relying on the latest released version is a bad idea.
Your experience proofs that it is indeed a very bad idea...
> 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
