|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-10449) Excluded regions do not exclude commits from changelog
brent.atkin...@gmail.com (JIRA) Fri, 14 Dec 2012 17:22:46 -0800
- [JIRA] (JENKINS-10449) Excluded regions do... brent.atkin...@gmail.com (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... brent.atkin...@gmail.com (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... brent.atkin...@gmail.com (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... brent.atkin...@gmail.com (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... brent.atkin...@gmail.com (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... brent.atkin...@gmail.com (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... leonov...@yandex.ru (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... brent.atkin...@gmail.com (JIRA)
It seems like it should be a simple matter of iterating through the changes generated for the changelog, and filtering them based on the same rules for the detection check. However, this is more complex than it seems at first.
The detection happens quite separately from the changelog generation. The detection happens in a private inner class in husdon.scm.SubversionSCM$SVNLogHandler.checkEntry, the handler is coupled to SVNKit's SVNLogEntry class. The changelog generation has its own LogEntry class, and there are a lot of private methods in SubversionSCM that it depends on, so you can't simply factor out the same code to filter them.