Community
Participate
Eclipse IDE
using a cvs 1.12.9 server, the 'Show in Resource History' command shows 'Not Available' in the 'Date' column. this seems to have something to do with a new feature in cvs 1.12.9: NEW FEATURES * `cvs log' & `cvs ls' now output local times when both the server and client are 1.12.9 or greater. see https://ccvs.cvshome.org/source/browse/ccvs/NEWS?rev=1.251&content-type=text/x-cvsweb-markup
Thanks for the heads-up. Because of the radical changes in the 1.12.X feature branch we can only ensure that our client is compatible with the stable 1.11.X releases to now. We will try our best to keep up with 1.12.X but we are too late to do anything for 3.0.
Is there any way to see the raw output from "cvs log"? I switched on CVS console logging but apparently there is nothing written for "Team -> Show in Resource History". Thx!
Follow the steps at ths URL: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm- home/docs/online/cvs_features2.0/cvs-faq.html#misc_0
*** Bug 69102 has been marked as a duplicate of this bug. ***
*** Bug 73395 has been marked as a duplicate of this bug. ***
Any chance this can be fixed? We're running CVS 1.12.xx with no other issues otherwise. 1.12 is now the main CVS release, and I think it's reasonable that Eclipse support it. Other tools like TortoiseCVS have no problem with the date. The lack of a date display in the revision history is extremely annoying.
It is my understanding that 1.12 is not a production release and never will be. I believe that, for CVS, even numbered releases are feature releases and odd numbered releases are stable releases. Regardless, I would say that there is a fair to good chance that I will have an opportunity to investigate and fix this bug for 3.1. Personally, I don't use 1.12.x so the fact that I would have to install the latest 1.12 release to diagnose the problem and fix it is one of the complicating factors. Of course, if someone who uses 1.12.9 (or beyond) with Eclipse was to provide a patch, that would increase the chances of this being fixed in 3.1 greatly;-)
the fix is pretty simple. we already patched our cvs team plugin here. i'll submit my patch for consideration. Steve Polyak
I can't find an official distinction betwee the stable (1.11) and feature (1.12) branch of CVS, but in mailing list posts when people have asked which to use, the feature version has certainly not been presented as a development only release. It's just not supposed to be as stable as there are more than bug fixes going in. Certainly they are recommending that people do use it for production use, if they are willing to tolerate some potential instability...
Created attachment 17200 [details] simple replace fix for the cvs 1.12.9 iso log format parsing problem fixes the problem getting dates from the new cvs iso log format added in cvs 1.29.9
Thanks for the patch. I will have a look as soon as possible.
I tested the patch on my installation, and it fixes the problem. Thanks Steve!
*** Bug 83519 has been marked as a duplicate of this bug. ***
I like the patch in 82483 because it makes the existance of two formats more explicit *** This bug has been marked as a duplicate of 82483 ***
+1 to 82483 patch
