> -----Original Message-----
> From: Luke Taylor [mailto:[EMAIL PROTECTED]
> Sent: 19 September 2003 21:06
> To: Maven Developers List
> Subject: Re: StatCvs 2.0-SNAPSHOT is ready for trial...
>
> Vincent Massol wrote:
>
> >
> >
> >>for the repository and the projects I would like to run against are
at
> >>Sourceforge which is still interminably slow for anonymous CVS
access.
> >>Is there any way to get it to make use of existing data rather than
> >>downloading the full log each time? (This is what I was trying to
> >>achieve with the MAVEN-562 patch to changelog).
> >
> >
> > Actually this already works. If you run when being offline (-o
switch)
> > it won't generate reports. I understand it's not exactly what you
want
> > but I don't really the usefulness of generating the reports if you
> > cannot connect. Same for any plugin requiring internet access.
> >
> 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?
Yes, I understood what you meant ;-) What I was saying was that I didn't
see the need to generate statcvs reports if you were not logged in.
What's important is simply that you are able to run maven site without
it failing. Using the -o option would do that. I find that a better
general solution to your problem rather than tweak each plugin with
internet access with special options.
I don't know what -use-history is about. In any case, it wouldn't help
as we're performing the cvs log before running statcvs.
>
> >
> >>Having had a quick look at the jelly script it looks like it's not
> >
> > using
> >
> >>the repository defined in project.xml:
> >>
> >> <!-- FIXME : We must use, with cvs, the connection string
> >
> > define
> >
> >> in project.xml -->
> >> <ant:cvs command="-q log" output="${statcvs.logfile}"/>
> >
> >
> > 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.
>
ok. So you're saying it should stay as it currently is. Cool.
WRT the cvs password: You have to provide a solution without having to
type a password (like uploading your public key to SF) and then using
putty/tortoisecvs or pageant or whatever else (putty/tortoisecvs is
really the best option I think).
-Vincent
> Luke.
>
> --
> Luke Taylor. Monkey Machine Ltd.
> PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
