|
||||||||
|
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-16208) TFS SCM Polling: FATAL: Pa... [email protected] (JIRA)
- [JIRA] (JENKINS-16208) TFS SCM Polling: FATA... [email protected] (JIRA)
- [JIRA] (JENKINS-16208) TFS SCM Polling: FATA... [email protected] (JIRA)
- [JIRA] (JENKINS-16208) TFS SCM Polling: FATA... [email protected] (JIRA)
- [JIRA] (JENKINS-16208) TFS SCM Polling: FATA... [email protected] (JIRA)
- [JIRA] (JENKINS-16208) TFS SCM Polling: FATA... [email protected] (JIRA)

Dig a little digging on this....looks like the problem is that our developer used "------------" within his changeset comment. This causes the code at line 247 of DetailedHistoryCommand (in the ChangeSetStringReader.readChangeSet method) to think that a new changeset is starting. We can fix the comment for now to avoid the problem. Is there any way to make the ChangeSetStringReader parser smarter somehow?