You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2009/12/03 18:52:55 UTC

[jira] Commented: (MCHANGES-141) Jira Report fails to pick up issues that contain multiple fix-for elements.

    [ http://jira.codehaus.org/browse/MCHANGES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200477#action_200477 ] 

Dennis Lundberg commented on MCHANGES-141:
------------------------------------------

I've had a look at the patch for this issue. Unfortunately it will not work. The problem is in JiraXML.getReleases() and this row:
{code}
releasesMap.put( fixIssue, release );
{code}
This means that only one of the releases for that issue will be in the List of releases that is returned from that method. The concept of using a Map keyed by issue doesn't work when you can have multiple releases per issue.

> Jira Report fails to pick up issues that contain multiple fix-for elements.
> ---------------------------------------------------------------------------
>
>                 Key: MCHANGES-141
>                 URL: http://jira.codehaus.org/browse/MCHANGES-141
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: jira-report
>    Affects Versions: 2.1
>            Reporter: Mark Derricutt
>         Attachments: multipleFixFors.patch
>
>
> When a jira ticket is associated with multiple versions in its fix-for list, the report fails to correctly report the issues.
> A patch is attached which collects each fix for into a List of strings, and updates the report to include them.

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