[ 
https://issues.jenkins-ci.org/browse/JENKINS-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158932#comment-158932
 ] 

SCM/JIRA link daemon commented on JENKINS-12586:
------------------------------------------------

Code changed in jenkins
User: Alex Lehmann
Path:
 src/main/java/hudson/scm/CVSChangeLogSet.java
 src/test/java/hudson/scm/CVSChangeLogParserTest.java
 src/test/resources/hudson/scm/changelogOldFormat.xml
http://jenkins-ci.org/commit/cvs-plugin/be6dd95edca7b4dbaf0125c6df0587d4b3c41e14
Log:
  [JENKINS-12586] cvs-plugin fails to read old changelog files
test and fix for the issue, old files contain date with yyyy-mm-DD and HH:mm, 
but the parser uses yyyy/mm/DD and HH:mm:ss



                
> cvs-plugin fails to read old changelog files
> --------------------------------------------
>
>                 Key: JENKINS-12586
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12586
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cvs
>    Affects Versions: current
>         Environment: jenkins 1.449, cvs-plugin 2.0
>            Reporter: Alex Lehmann
>            Priority: Minor
>
> after updating to cvs-plugin 2.0, I get an exception when parsing the old 
> changelog files that were written by the previous version of the plugin, e.g.
> Caused by: java.text.ParseException: Unparseable date: "2011-12-14"
>         at java.text.DateFormat.parse(DateFormat.java:337)
>         at 
> hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:232)
>         ... 34 more
> the corresponding changelog entry looks like this
> <changelog>
>         <entry>
>                 <date>2011-12-14</date>
>                 <time>23:26</time>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to