Luke Taylor wrote:
So I think it would require a bit of work to implement this. Have to
look at what it's doing first though to be sure. It would be useful
though - I don't fancy retrieving a full log for a project like JBoss
(for example) every time I run Maven. I'm still waiting for my recentl
StatCVS takes ages to run compared to changelog, and from what I can tell
it doesn't do *all* that changelog does.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Luke Taylor <[EMAIL PROTECTED]> wrote on 24/09/2003 09:49:27 AM:
> Rafal Krzewski wrote:
> >
Rafal Krzewski wrote:
I think the best apporoach would be enchancing statcvs with pluggable
log parsers, and implement a parser for maven-chngelog-plugin
changes.xml files. It shouldn't be very complicated. I don't know if
statcvs folks hang aroud here. If they don't respond soon maybe you,
(Lu
Luke Taylor wrote:
>> I've just realized that this is more complex than I thought. You can't
>> combine cvs log output by concatenating. To take advantage of that the
>> revision information would have to be stored in a processed from, to
>> faciliate reading it, combining and storing again.
>
>
Fabrizio,
and alternative to extssh is just to use ext, and set CVS_RSH to point to
ssh.
I use this with eclipse and maven.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Fabrizio Giustina" <[EMAIL PROTECTED]> wrote on 23/09/2003 08:40:27
AM:
>
> >>
>>
>> Having had a quick look at the jelly script it looks like it's not
using
>> the repository defined in project.xml:
>>
>>
>>
> 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
m
Rafal Krzewski wrote:
Rafal Krzewski wrote:
Saving the bandwidth is definetely a good thing. I'm wondering if it
is possible to avoid downloading a complete log file on each run. I
imagine
that if you saved the login in ~/.statcvs along with a timestamp, and
use a cvs log -D on the next run yo
release it. In any case, I'll release it tonight (and of course
put it on ibiblio).
Thanks
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 21 September 2003 15:50
> To: Maven Developers List
> Subject: RE: StatCvs 2.0-SNAPS
; wrote on 21/09/2003 08:38:06 PM:
> Of course!
>
> http://www.ibiblio.org/maven/statcvs/jars/
>
> -Vincent
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: 21 September 2003 12:29
> > To: Maven Develope
Of course!
http://www.ibiblio.org/maven/statcvs/jars/
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 21 September 2003 12:29
> To: Maven Developers List
> Subject: Re: StatCvs 2.0-SNAPSHOT is ready for trial...
>
Is it on ibiblio?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 20/09/2003 01:00:55 AM:
> Hi,
>
> Could some of you test the new statcvs plugin I have just committed and
> tell me if it works. I'd like to re
Rafal Krzewski wrote:
Saving the bandwidth is definetely a good thing. I'm wondering if it is
possible to avoid downloading a complete log file on each run. I imagine
that if you saved the login in ~/.statcvs along with a timestamp, and
use a cvs log -D on the next run you could just combine the
Tammo van Lessen wrote:
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 fi
> 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 info
> -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 re
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 t
> -Original Message-
> From: Luke Taylor [mailto:[EMAIL PROTECTED]
> Sent: 19 September 2003 18:44
> To: Maven Developers List
> Subject: Re: StatCvs 2.0-SNAPSHOT is ready for trial...
>
> Vincent Massol wrote:
>
> > Hi,
> >
> > Could some of y
Vincent Massol wrote:
Hi,
Could some of you test the new statcvs plugin I have just committed and
tell me if it works. I'd like to release it over the next 2 days so that
it is released before the 1.0 rc1 release of Monday.
http://maven.apache.org/reference/plugins/statcvs/
Here's an output exam
18 matches
Mail list logo