netbeans/cvslib jar needs updating [was Still having problem parsing cvs dates]

[Tim Pizey <ti...@paneris.org>]

Hi, 

The problems with cvs date handling reported in 
http://jira.codehaus.org/browse/MAVEN-1447
have been fixed in netbeans version 4.1 
http://www.netbeans.org/source/browse/javacvs/libsrc/org/netbeans/lib/cvsclient/command/log/LogInformation.java?r1=1.15&r2=1.16

The current maven-1.1.-beta-2 is still shipping with a jar 
called cvslib-3.6.jar

If one copies the ide5/modules/org-netbeans-lib-cvsclient.jar from a 
netbeans 4.1 installation to ~/.maven/repository/netbeans/jars/cvslib-3.6.jar 
then the problem goes away. 

Hope this helps
Tim Pizey



On Friday 16 September 2005 10:55, Tim Pizey wrote:
> Hi,
>
> For some while now I have had problems with cvs dates.
>
> I have just installed maven-1.1.-beta-2 in the hope that that would cure
> it, but no.
>
> The server was running cvs-1.12.9 which seemed to introduce this problem.
> I have now upgraded the server to 1.12.12, which my client is also running,
> but the problem persists:
>
> java.lang.Exception: Couldn't parse date 2003-07-15 11:56:29 +0000
>         at org.netbeans.lib.cvsclient.util.BugLog.bug(BugLog.java:58)
>         at
> org.netbeans.lib.cvsclient.command.log.LogInformation$Revision.setDateStrin
>g(LogInformation.java:382) at
> org.netbeans.lib.cvsclient.command.log.LogBuilder.processRevisionDate(LogBu
>ilder.java:273) at
> org.netbeans.lib.cvsclient.command.log.LogBuilder.parseLine(LogBuilder.java
>:134) at
> org.netbeans.lib.cvsclient.command.BuildableCommand.messageSent(BuildableCo
>mmand.java:86) at
> org.netbeans.lib.cvsclient.event.MessageEvent.fireEvent(MessageEvent.java:9
>6) at
> org.netbeans.lib.cvsclient.event.EventManager.fireCVSEvent(EventManager.jav
>a:107) at
> org.netbeans.lib.cvsclient.response.MessageTaggedResponse.process(MessageTa
>ggedResponse.java:39) at
> org.netbeans.lib.cvsclient.Client.handleResponse(Client.java:485) at
> org.netbeans.lib.cvsclient.Client.processRequests(Client.java:439) at
> org.netbeans.lib.cvsclient.command.log.LogCommand.execute(LogCommand.java:1
>32) at org.netbeans.lib.cvsclient.Client.executeCommand(Client.java:533) at
> org.apache.maven.cvslib.CvsConnection.executeCommand(CvsConnection.java:90)
>         at
> org.apache.maven.cvslib.CvsConnection.processCommand(CvsConnection.java:436
>) at
> org.apache.maven.cvslib.CvsChangeLogGenerator.getEntries(CvsChangeLogGenera
>tor.java:100) at
> org.apache.maven.changelog.ChangeLog.generateSets(ChangeLog.java:423)
>         at
> org.apache.maven.changelog.ChangeLog.doExecute(ChangeLog.java:368) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
>9) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
>l.java:25) at java.lang.reflect.Method.invoke(Method.java:324)
>         at
> org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:180)
>         at
> org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript
>
>
> http://jira.codehaus.org/browse/MAVEN-1447 suggests that the problem is not
> with maven/netbeans and to search the ML, which I have done with no sucess.
>
> The date appears, to my naive eye, to be OK, any suggestions as to what I
> need to do to fix this, do I need to do some cvs surgery?
> There are a few of these rogue dates.
>
>
> yours
> Tim P
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org