Isn't in a lot easier if the Subversion commit details are available directly from the JIRA issue, either via the commit tab or as a comment?
Also not difficult to do - just paste the commit header into the comment box when resolving the issue. 2011/6/5 Arnaud Héritier <[email protected]>: > There was an integration with fisheye and our SVN before but I think that > Ben (aka Codehaus) had a lot of performances issues with it. > I found an old maven repo in fisheye but it is no more updated that's > probably why it isn't configured in the project : > https://fisheye.codehaus.org/changelog/maven/repository/maven > We can discuss with Ben to see if we can fix it. > > On Sun, Jun 5, 2011 at 1:48 AM, Benson Margulies <[email protected]>wrote: > >> I have been. Did I miss one? >> >> This is generally a job for fisheye, after all. >> >> On Sat, Jun 4, 2011 at 7:45 PM, sebb <[email protected]> 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. >> > >> >> >> >>> >> >>> --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] >> > >> > >> >> --------------------------------------------------------------------- >> 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]
