You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2011/05/01 00:36:22 UTC

[jira] Closed: (MPIR-223) Dependency report introduces corruption in classpaths for other plugins

     [ http://jira.codehaus.org/browse/MPIR-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy closed MPIR-223.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.2
         Assignee: Herve Boutemy

fixed in [r1098179|http://svn.apache.org/viewvc?rev=1098179&view=rev], with an IT to ensure the bug won't reappear

> Dependency report introduces corruption in classpaths for other plugins
> -----------------------------------------------------------------------
>
>                 Key: MPIR-223
>                 URL: http://jira.codehaus.org/browse/MPIR-223
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: Bug
>          Components: dependencies
>    Affects Versions: 2.3, 2.3.1
>            Reporter: Carlos Sanchez
>            Assignee: Herve Boutemy
>             Fix For: 2.3.2
>
>         Attachments: maven-project-info-report-defect-2.3.1.zip
>
>
> MPIR-144 shows up again per Neil Hartner comments. Creating this new issue
> ====
> This issue has reappeared in 2.3.1. I'm attaching an updated version of the zipped maven project that reproduces this issue. You can change which version of MPIR plugin to use with -Dmpir-version. For example:
> mvn clean install site:site -Dmpir-version=2.3.1
> 2.1, 2.3 and 2.3.1 will fail
> 2.1.1 and 2.2 will succeed

-- 
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