My gut feeling is this is just WinCvs messing up the timestamps again or something, on the other hand I would have thought prettyprinter should be able to cope with dodgy timestamps without crashing. Any chance this exception's something to do with how prettyprinter was jar'ed up, or is it just a jrefactory bug/limitation?
... [pretty] formatting:D:\JavaApps\xdoclet\xdoclet\core\src\xdoclet\ejb\EjbDotXmlSubTa sk.java [pretty] formatting:D:\JavaApps\xdoclet\xdoclet\core\src\xdoclet\jmx\MBeanInterface SubTask.java [pretty] formatting:D:\JavaApps\xdoclet\xdoclet\core\src\xdoclet\jmx\JMXDocletTask. java [pretty] java.lang.NullPointerException [pretty] at org.acm.seguin.ant.CVSUtil$CVSEntry.equalsTime(CVSUtil.java:296) [pretty] at org.acm.seguin.ant.CVSUtil.isFileModified(CVSUtil.java:99) [pretty] at org.acm.seguin.ant.Pretty.execute(Pretty.java:129) [pretty] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:104) [pretty] at org.apache.tools.ant.Task.perform(Task.java:217) [pretty] at org.apache.tools.ant.Target.execute(Target.java:164) ... In fact, come to think of it there's a couple of files whose CVS/entries record doesn't have a date, just "Result of merge". Maybe that's the problem? _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
