[
http://jira.codehaus.org/browse/MCHANGES-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SebbASF reopened MCHANGES-253:
------------------------------
Sorry, but there is still an incorrect mention of closed - I've just checked in
the current source, i.e.
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-changes-plugin/src/site/apt/examples/customizing-jira-report.apt.vm?revision=1131414
{quote}
** Using Maven syntax
In the following example we are only including issues that have <Closed> as
their resolution. The status must be either <Resolved> or <Closed>. Only
...
<configuration>
<resolutionIds>Fixed</resolutionIds>
<statusIds>Resolved, Closed</statusIds>
...
{quote}
Closed is not valid as a resolution.
> Documentation bug - "Closed" is not a resolutionID
> ---------------------------------------------------
>
> Key: MCHANGES-253
> URL: http://jira.codehaus.org/browse/MCHANGES-253
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: jira
> Affects Versions: 2.5
> Environment:
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> Reporter: SebbASF
> Assignee: Benson Margulies
> Fix For: 2.6
>
>
> The page
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
> says:
> {quote}
> Using Maven syntax
> In the following example we are only including issues that have Closed as
> their resolution.
> {quote}
> However, as far as I can tell, Closed is not a valid Resolution type.
> It should probably be "Fixed".
--
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
