[ http://jira.codehaus.org/browse/MCHANGES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MCHANGES-254: -------------------------------------- Fix Version/s: 2.6 > Example doesn't work - spaces not allowed in statusIds and resolutionIds after a comma > -------------------------------------------------------------------------------------- > > Key: MCHANGES-254 > URL: http://jira.codehaus.org/browse/MCHANGES-254 > 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 > > > http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html#Using_Maven_syntax > gives the following examples: > {quote} > > Closed > Resolved, Closed > Bug, New Feature, Improvement, Wish > > {quote} > However, spaces are not always allowed, they can cause the field to be ignored. > Resolved,Closed - OK > Resolved,Closed - OK > Resolved,Closed - OK > Resolved,Closed - OK > Resolved, Closed - Closed is ignored > Resolved, Closed - Closed is ignored > Resolved, Closed - Closed is ignored > In particular, the example from the web page does not work. > Note that the typeIds field does appear to allow leading space after a comma. > The resolutionIds field does not. > Since spaces are sometimes allowed, may I suggest the code is fixed rather than the documentation? -- 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