On 4/27/06, Ben Alex <[EMAIL PROTECTED]> wrote: > For the sake of consistency and ease of reviewing history logs, would > developers please always format SVN commit messages to begin with the > JIRA issue number, followed by a colon, then a brief description of the > check-in. More detailed messages can be placed in the JIRA task. eg: > > SEC-123: Constructor no longer requires null.
Sorry if I'm teaching granny to suck eggs here, but have you seen jira's svn plugin: http://confluence.atlassian.com/display/JIRAEXT/JIRA+Subversion+plugin The integration polls and indexes the svn logs hourly with lucene, rather than use post-commit triggers. The indexing means it'll show links to revisions before you installed the plugin, and the format you described should be picked up fine. (I havent set this one up myself, just the trigger-based integration for fogbugz, which isnt as nice). Cheers Baz ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
