> Ummm. I think the wires got crossed a bit here. I wasn't meaning > situations where it wasn't possibl to connect, just that doing "cvs log" > for the entire history of the project can be quite an expensive > operation and would take ages with sourceforge. If you have already > downloaded the information on a previous run then it would be more > efficient to specify start and end dates and just retrieve what's new. > I noticed there's a "-use-history" parameter for statcvs in there - is > that connected with this kind of thing?
Nope, we introduced the history to provide a (more) correct loc count (and charts) than the original statcvs does. cvs log doesnt report the loc of the first revision but the changes for the following revisions. To get the right loc count, we need to know the count of the first revision. On the first use, statcvs-xml checks out the first revision for all files and stores its loc count in the history file. This is needed to track the (almost) correct loc count, even if you delete some files. Oh, and you need to create a ~/.statcvs/ directory, otherwise the history can not be saved. this is a bug and will be fixed as soon as possible. [...] > > Actually, I wrote that comment ages ago and I'm not sure we need to use > > the repo defined in project.xml. If you used the repo of basedir it must > > always be correct, right? > > How will this work if the project uses cvs over ssh. Won't there be a > problem with logging in? I just tried "maven statcvs" in a project which > uses my sf login and it just hangs. There may be a workaround with the > ssh agent or something but I've always just supplied my password in the > past. Using the developer login would actually be preferable over > anonymous cvs as sf allocates much higher bandwidth in this case. On Windows, you have to upload your keys while windows wont show ssh's password prompt if its get started out of maven. On Linux, this should work properly. Tammo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
