|
||||||||
|
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... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)

This is more complex than it seems at first. The detection happens quite separately from the changelog generation. Also, in husdon.scm.SubversionSCM$SVNLogHandler.checkEntry, the handler is coupled to SVNKit and its SVNLogEntry class. The changelog generation has its own LogEntry class, so you can't simply reuse the same code to filter them.