Unparseable date

Bug #534959 reported by Aliaksei Vasileuski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr4j
Fix Committed
Undecided
Aliaksei Vasileuski

Bug Description

failed to parse: Fri 2009-03-27 18:41:19 +0000: Unparseable date: "Fri 2009-03-27 18:41:19 +0000"
java.text.ParseException: Unparseable date: "Fri 2009-03-27 18:41:19 +0000"
 at java.text.DateFormat.parse(DateFormat.java:337)
 at org.emergent.bzr4j.core.xmloutput.XmlOutputHandler.handleLog(XmlOutputHandler.java:47)
 at org.emergent.bzr4j.core.xmloutput.XmlOutputHandler.handleChange(XmlOutputHandler.java:64)
 at org.emergent.bzr4j.core.xmloutput.XmlOutputHandler.endElement(XmlOutputHandler.java:234)
 at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
 at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
 at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
 at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
 at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
 at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
 at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:198)
 at org.emergent.bzr4j.core.cli.BzrXmlResult$1.run(BzrXmlResult.java:66)
 at java.lang.Thread.run(Thread.java:619)

Related branches

Revision history for this message
Aliaksei Vasileuski (sagara1337) wrote :

I fixed it, hope to publish a branch later.

Changed in bzr4j:
status: New → Fix Committed
assignee: nobody → Nishi (sagara1337)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.