On 6 June 2011 09:23, Dennis Lundberg <[email protected]> wrote: > On 2011-06-05 01:45, sebb wrote: >> On 4 June 2011 22:02, Dennis Lundberg <[email protected]> wrote: >>> On 2011-06-04 22:44, Benson Margulies wrote: >>>> Dennis, >>>> >>>> Points taken. The web page with developer guidance does specifically >>>> give the syntax: >>>> >>>> [JIRA1, JIRA2, ...] comments >>> >>> Indeed they do. >>> Looks like I have some site docs to update :) >> >> Unfortunately, it looks like Codehaus JIRA is not set up to add SVN >> log messages to issue comments, so the SVN ids need to be added >> manually to the issues. > > Yes, I keep this snippet on my desktop and copy/paste it into JIRA when > resolving an issue: > > Fixed in > [r1129889|http://svn.apache.org/viewvc?view=revision&revision=1129889]. > > Just remember to change the revision number.
Why not pick up the details from the SVN log message? You can then include the list of files as well. For example: URL: http://svn.apache.org/viewvc?rev=1131414&view=rev Log: [MCHANGES-254, MCHANGES-253] add more calls to trim, fix doc. Also fix some warnings in site generation. Modified: maven/plugins/trunk/maven-changes-plugin/pom.xml maven/plugins/trunk/maven-changes-plugin/src/main/java/org/apache/maven/plugin/jira/AbstractJiraDownloader.java maven/plugins/trunk/maven-changes-plugin/src/main/java/org/apache/maven/plugin/jira/JiraXML.java maven/plugins/trunk/maven-changes-plugin/src/site/apt/examples/customizing-jira-report.apt.vm maven/plugins/trunk/maven-changes-plugin/src/site/apt/usage.apt.vm >> >>> >>>> >>>> --benson >>>> >>>> >>>> On Sat, Jun 4, 2011 at 4:33 PM, Dennis Lundberg <[email protected]> wrote: >>>>> On 2011-06-04 22:16, sebb wrote: >>>>>> On 4 June 2011 21:04, Dennis Lundberg <[email protected]> wrote: >>>>>> >>>>>> ... >>>>>> >>>>>>> 2. Please use the following form for the commit messages: >>>>>>> >>>>>>> [<issueId>] <issueSummary> >>>>>>> >>>>>>> for example: >>>>>>> >>>>>>> [MCHANGES-254] Example doesn't work - spaces not allowed in statusIds >>>>>>> and resolutionIds after a comma >>>>>> >>>>>> +1 >>>>>> >>>>>> It would be useful to have done this for r1131484 as well. >>>>>> >>>>>> I.e. instead of >>>>>> >>>>>> "Fix typo from r1131414 ." >>>>>> >>>>>> the log message could have been: >>>>>> >>>>>> "[MCHANGES-254] Example doesn't work - spaces not allowed in statusIds >>>>>> and resolutionIds after a comma >>>>>> Fix bug introduced in r1131414" >>>>>> >>>>>> which would help tie it to the original issue. >>>>>> >>>>>> AFAIK, it's not too late to fix the log messages ... >>>>> >>>>> Right. I've fixed the commit message for r1131484 now. >>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Dennis Lundberg >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> >>> -- >>> Dennis Lundberg >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
