|
||||||||
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-15525) ProjectSet parser isn't working
felix.vela...@gmail.com (JIRA) Tue, 16 Oct 2012 00:25:48 -0700
- [JIRA] (JENKINS-15525) ProjectSet parser... felix.vela...@gmail.com (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... felix.vela...@gmail.com (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... ralf.eis...@gmx.de (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... ralf.eis...@gmx.de (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15525) ProjectSet p... scm_issue_l...@java.net (JIRA)
Regarding your points:
1. I thought that colon was mandatory, not optional. That's why I took it out of the optional part
2. My bad, I put the slash in the wrong place (most embarrassingly, since I need that slash in the middle of the remote module name).
However, I honestly believe regexp is way too complicated, error-prone and hard to maintain for this job. Just a couple of StringTokenizers, first using commas, then colons for the cvsroot, should be enough. Just my two cents.
Anyway, the committed change works perfectly for my psfs. Thank you!