You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2008/02/02 23:34:58 UTC

[jira] Created: (MJAVADOC-172) classpath is wrong using aggregate mode

classpath is wrong using aggregate mode
---------------------------------------

                 Key: MJAVADOC-172
                 URL: http://jira.codehaus.org/browse/MJAVADOC-172
             Project: Maven 2.x Javadoc Plugin
          Issue Type: Bug
    Affects Versions: 2.3
            Reporter: Vincent Siveton
            Priority: Blocker


When aggregate mode is used, the populateCompileArtifactMap( Map compileArtifactMap, List artifactList ) doesn't take care of the artifact version in the key.
So, an unwanted artifact could be used instead of the wanted artifact version

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

[jira] Closed: (MJAVADOC-172) classpath is wrong using aggregate mode

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MJAVADOC-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Siveton closed MJAVADOC-172.
------------------------------------

         Assignee: Vincent Siveton
       Resolution: Fixed
    Fix Version/s: 2.4

fixed in r617918

> classpath is wrong using aggregate mode
> ---------------------------------------
>
>                 Key: MJAVADOC-172
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-172
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>            Reporter: Vincent Siveton
>            Assignee: Vincent Siveton
>            Priority: Blocker
>             Fix For: 2.4
>
>
> When aggregate mode is used, the populateCompileArtifactMap( Map compileArtifactMap, List artifactList ) doesn't take care of the artifact version in the key.
> So, an unwanted artifact could be used instead of the wanted artifact version

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