You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Siegfried Göschl <si...@it20one.at> on 2003/04/23 14:48:26 UTC
Capturing of historical project data ...
Hi folks,
are there any plans for capturing historical data?!
+) CLOVER 1.1 provides not historical coverage data
+) Code growth over the time might be interesting
+) Same for the PMD reports and number of test cases
If everything works out nicely I can add historical reports to the
CLOVER plugin ....
Thanks in advance
Siegfried Goeschl
CTO
=================================
IT20one GmbH
mail: siegfried.goeschl@it20one.at
phone: +43-1-9900046
fax: +43-1-52 37 888
www.it20one.at
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Capturing of historical project data ...
Posted by Siegfried Göschl <si...@it20one.at>.
My favourite tool for simple source code metrics is SourceMonitor
from James F. Wanner.
On 23 Apr 2003 at 15:09, Juergen Heidak wrote:
> I'm very interested in historical data, every (code) metric becomes
> more powerful if it can be compared to older versions.
>
> Am Mittwoch, 23. April 2003 14:48 schrieb Siegfried Göschl:
> > Hi folks,
> >
> > are there any plans for capturing historical data?!
> >
> > +) CLOVER 1.1 provides not historical coverage data
> > +) Code growth over the time might be interesting
> > +) Same for the PMD reports and number of test cases
> >
> >
> > If everything works out nicely I can add historical reports to the
> > CLOVER plugin ....
> >
> > Thanks in advance
> >
> > Siegfried Goeschl
> > CTO
> > =================================
> > IT20one GmbH
> > mail: siegfried.goeschl@it20one.at
> > phone: +43-1-9900046
> > fax: +43-1-52 37 888
> > www.it20one.at
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Capturing of historical project data ...
Posted by Siegfried Göschl <si...@it20one.at>.
Hi Juergen,
my favorite tool for capturing historical source code metrics is
SourceMonitor from James F. Wanner.
He upgraded SourceMonitor recently to separate the report generator
from the user interface written in C++ for Windows. The report
generator can be driven with XML command files to generate XML
reports.
You can have a look at
http://www.campwoodsw.com/smbeta.html
The cool feature is the checkpointing of historical data. I'm playing
with the thought of wrapping SourceMonitor into a Maven plugin and
create charts using SVG ... but no time at the moment
Cheers,
Siegfried Goeschl
CTO
=================================
IT20one GmbH
mail: siegfried.goeschl@it20one.at
phone: +43-1-9900046
fax: +43-1-52 37 888
www.it20one.at
On 23 Apr 2003 at 15:09, Juergen Heidak wrote:
> I'm very interested in historical data, every (code) metric becomes
> more powerful if it can be compared to older versions.
>
> Am Mittwoch, 23. April 2003 14:48 schrieb Siegfried Göschl:
> > Hi folks,
> >
> > are there any plans for capturing historical data?!
> >
> > +) CLOVER 1.1 provides not historical coverage data
> > +) Code growth over the time might be interesting
> > +) Same for the PMD reports and number of test cases
> >
> >
> > If everything works out nicely I can add historical reports to the
> > CLOVER plugin ....
> >
> > Thanks in advance
> >
> > Siegfried Goeschl
> > CTO
> > =================================
> > IT20one GmbH
> > mail: siegfried.goeschl@it20one.at
> > phone: +43-1-9900046
> > fax: +43-1-52 37 888
> > www.it20one.at
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
Siegfried Goeschl
CTO
=================================
IT20one GmbH
mail: siegfried.goeschl@it20one.at
phone: +43-1-9900046
fax: +43-1-52 37 888
www.it20one.at
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Capturing of historical project data ...
Posted by Juergen Heidak <Ju...@Heidak.de>.
I'm very interested in historical data, every (code) metric becomes more
powerful if it can be compared to older versions.
Am Mittwoch, 23. April 2003 14:48 schrieb Siegfried Göschl:
> Hi folks,
>
> are there any plans for capturing historical data?!
>
> +) CLOVER 1.1 provides not historical coverage data
> +) Code growth over the time might be interesting
> +) Same for the PMD reports and number of test cases
>
>
> If everything works out nicely I can add historical reports to the
> CLOVER plugin ....
>
> Thanks in advance
>
> Siegfried Goeschl
> CTO
> =================================
> IT20one GmbH
> mail: siegfried.goeschl@it20one.at
> phone: +43-1-9900046
> fax: +43-1-52 37 888
> www.it20one.at
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Capturing of historical project data ...
Posted by Siegfried Göschl <si...@it20one.at>.
On 23 Apr 2003 at 15:18, Vincent Massol wrote:
>
>
> > -----Original Message-----
> > From: Siegfried Göschl [mailto:siegfried.goeschl@it20one.at]
> > Sent: 23 April 2003 14:48
> > To: dev@maven.apache.org
> > Subject: Capturing of historical project data ...
> >
> > Hi folks,
> >
> > are there any plans for capturing historical data?!
> >
> > +) CLOVER 1.1 provides not historical coverage data
>
> I guess you meant that it does, right? :-)
Sorry for the typo ....
>
> > +) Code growth over the time might be interesting
> > +) Same for the PMD reports and number of test cases
> >
> >
> > If everything works out nicely I can add historical reports to the
> > CLOVER plugin ....
>
> +1!
Thanks for the first "+1!" in my developer live ...
>
> However, I'm not sure how you would do that as project artifacts are
> not saved in CVS... You would need to find some storage for them,
> possibly in the remote repository?
>
IMHO historical data can/should be saved in the CVS repository
otherwise they will be lost. Having said that it is probably easier
to consider the historical CLOVER database as project artifact since
I don't have to wrestle with CVS commit and non-CVS systems.
> -Vincent
>
> >
> > Thanks in advance
> >
> > Siegfried Goeschl
> > CTO
> > =================================
> > IT20one GmbH
> > mail: siegfried.goeschl@it20one.at
> > phone: +43-1-9900046
> > fax: +43-1-52 37 888
> > www.it20one.at
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
Siegfried Goeschl
CTO
=================================
IT20one GmbH
mail: siegfried.goeschl@it20one.at
phone: +43-1-9900046
fax: +43-1-52 37 888
www.it20one.at
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Console usage pattern
Posted by Florin Vancea <fv...@maxiq.ro>.
I have a question for whoever might want to answer it.
This is an issue I do not know if it's a bug or a known feature/limitation,
so I'd like to hear from the authorized persons an opinion before making it
a JIRA feature request of bug report.
The console plugin allows one to load Maven once and then repeatedly invoke
goals, without the time penalty of reinitializing the build system every
time. I am very interested in such usage pattern and I even wrote my own
version of CLI that does approximately what the console plugin does.
Now the problem is that if one of the artifacts listed as dependencies gets
changed while the "persistent Maven" is loaded, even if Ben's last solution
to MAVEN-412 _does_ download the new stuff, it never gets loaded. The
classloader has already loaded the first version and is happy with it. This
happens unless all "things inside" are run forked (which denies the
usefulness of the console mode).
If any further proof is needed after the above (fuzzy) explanation, here is
the steps to reproduce the issue:
1. start "maven console" on a project (ABC) that depends on SNAPSHOT-version
of artifact XYZ.
2. run "test" or even just "java:compile". Let's presume it works.
3. leave this console alone and change the project XYZ in a separate shell.
Let's say we alter the API or maybe we do some less radical changes, like
printing a message on System.out during a message that gets called when we
_test_ the ABC project.
4. deploy XYZ in its changed form to repository
5. run "clean" "java:compile" or "clean" "test" on the ABC's "maven
console", which is still open.
The jar of XYZ is properly downloaded (thanks to Ben's recent changes), but:
- if we changed the API of XYZ in a incompatible way, the compile will still
be happy. Not what I'd expect.
- if we added that System.out.println(..) for test purposes, it does not
show during the test, meaning we are still using the old version of the XYZ
classes.
Yes, I know that:
- closing and re-opening "Maven console" will make the changes visible.
- using Maven in "single-shot" mode has no problems.
- any automated build will catch the problems generated due to such
behavior.
but:
- is this known-enough? I haven't seen any reference in the available docs.
- is this expected behavior? IMHO, it denies the purpose itself of using the
console or any equivalent of it.
- is this fixable without a "grass-root" change in the way classloading is
done?
I hope that I'm not chasing my own ghosts here. Please excuse me if so.
Florin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Capturing of historical project data ...
Posted by Tom Copeland <to...@infoether.com>.
On Wed, 2003-04-23 at 09:51, Siegfried Göschl wrote:
> Hi Tom,
>
> I had a look at CVS Monitor recently (no installation)
>
> http://ali.as/devel/cvsmonitor/index.html
Pretty cool!
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Capturing of historical project data ...
Posted by Siegfried Göschl <si...@it20one.at>.
Hi Tom,
I had a look at CVS Monitor recently (no installation)
http://ali.as/devel/cvsmonitor/index.html
It is a perl program running as CVS client on UNIX
Thanks,
Siegfried Goeschl
CTO
=================================
IT20one GmbH
mail: siegfried.goeschl@it20one.at
phone: +43-1-9900046
fax: +43-1-52 37 888
www.it20one.at
On 23 Apr 2003 at 9:38, Tom Copeland wrote:
> > > +) Code growth over the time might be interesting
>
> One way to get this info is to use StatCVS - http://statcvs.sf.net/.
> Here's an example chart:
>
> https://ultraforge.ultralog.net/statcvs/
>
> Sweet, huh? StatCVS rocks.
>
> > > +) Same for the PMD reports and number of test cases
>
> One way to get historical data would be to put PMD in a loop and have
> something like:
>
> cvs -Q co -D "2 days ago" mymodule
>
> and replacing "2" with the loop index, of course. This is a real
> pain, though... just an idea.
>
> Yours,
>
> Tom
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Capturing of historical project data ...
Posted by Tom Copeland <to...@infoether.com>.
> > +) Code growth over the time might be interesting
One way to get this info is to use StatCVS - http://statcvs.sf.net/.
Here's an example chart:
https://ultraforge.ultralog.net/statcvs/
Sweet, huh? StatCVS rocks.
> > +) Same for the PMD reports and number of test cases
One way to get historical data would be to put PMD in a loop and have
something like:
cvs -Q co -D "2 days ago" mymodule
and replacing "2" with the loop index, of course. This is a real pain,
though... just an idea.
Yours,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Capturing of historical project data ...
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Siegfried Göschl [mailto:siegfried.goeschl@it20one.at]
> Sent: 23 April 2003 14:48
> To: dev@maven.apache.org
> Subject: Capturing of historical project data ...
>
> Hi folks,
>
> are there any plans for capturing historical data?!
>
> +) CLOVER 1.1 provides not historical coverage data
I guess you meant that it does, right? :-)
> +) Code growth over the time might be interesting
> +) Same for the PMD reports and number of test cases
>
>
> If everything works out nicely I can add historical reports to the
> CLOVER plugin ....
+1!
However, I'm not sure how you would do that as project artifacts are not
saved in CVS... You would need to find some storage for them, possibly
in the remote repository?
-Vincent
>
> Thanks in advance
>
> Siegfried Goeschl
> CTO
> =================================
> IT20one GmbH
> mail: siegfried.goeschl@it20one.at
> phone: +43-1-9900046
> fax: +43-1-52 37 888
> www.it20one.at
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org