jmove-users — jmove users discussions

Re: [Jmove-users] Status

[Stefano F. <ste...@li...>]

Hi Axel, thank you very much for this. I will try soon.
I have just one more question:

> implementation with one of the next releases. It'll be an extension to 
> jmove which will be deploed on it's own (seperate jar) since we will 
> provide it under a more restricted licence than LGPL (perhaps GPL).

Is there a particular reason for this? I do not like virulent licenses 
such as GPL.... :(

Stefano

Re: [Jmove-users] Status

[Axel T. <ax...@sp...>]

Hi Stefano,

>> I hope this answer will help you a bit. If you have further questions 
>> just ask. For us it is also interesting to know more about your 
>> personal requirements. So it would be nice if you let us know what 
>> kind of metrics or other functionality you would like to find in jmove.
>>
> 
> What I would like to have is a tool that could work with or without a 
> gui. Without a gui, I would like specify the directory of my sources and 
>  it should produce an output with the calculated metrics per each unit 
> (package, class, method). An XML format should suffice. It would be nice 
> if the output was hierarchical and contained aggregated metrics.
> The gui should provide the same information, but browsable with a tree 
> view starting listing the packages and displaying for each of them the 
> dependency metrics and the aggragate metrics for the contained classes. 
> At a class level I sould see the class-level metrics and the aggragate 
> metrics for the methods... and so on (if possible :-).

Your wishes matches some of the thoughts we made concerning reporting 
model informations. I think we will provide a first simple 
implementation with one of the next releases. It'll be an extension to 
jmove which will be deploed on it's own (seperate jar) since we will 
provide it under a more restricted licence than LGPL (perhaps GPL).

> Those are my whishes. But for now it would be very nice if you could 
> show me a piece of code that basically kicks off the dependency metrics 
> and the counting metrics for a given package. I tried to go through the 
> test classes, but it is very hard to get the one at the right level of 
> detail.

Please take a look at the current example classes:

1. org.jmove.examples.java.DumpRCMartinMetrics.java
This example loads the model from bytecode (jmove itself in this case). 
Then it iterates through all packages and dumps the metrics to 
System.out. So for your purpose you can:

- simply copy the code
- modify getModel() to analyse your own classes
- perhaps replace System.out by any stream type you require

It should be easy to produce well formed xml output. If you require 
hierarchical output which matches the package hierarchy you of course 
have to refactor the while loop in main().

2. org.jmove.examples.java.LineCountExample
This example analyses the java source from a directory and accesses the 
line count metrics of types and methods. Therefor it iterates through 
all types available.

It is possible to mix both examples. The dependency metrics will also 
work with source code analysis. Let us know if things remain unclear. If 
there are fouther points wich can be demonstrated by examples them we 
may extend the examples.


Axel

Re: [Jmove-users] Status

[Stefano F. <ste...@li...>]

Hi Axel,
I hope you rested from the party :)

> I hope this answer will help you a bit. If you have further questions 
> just ask. For us it is also interesting to know more about your personal 
> requirements. So it would be nice if you let us know what kind of 
> metrics or other functionality you would like to find in jmove.
> 

What I would like to have is a tool that could work with or without a 
gui. Without a gui, I would like specify the directory of my sources and 
  it should produce an output with the calculated metrics per each unit 
(package, class, method). An XML format should suffice. It would be nice 
if the output was hierarchical and contained aggregated metrics.
The gui should provide the same information, but browsable with a tree 
view starting listing the packages and displaying for each of them the 
dependency metrics and the aggragate metrics for the contained classes. 
At a class level I sould see the class-level metrics and the aggragate 
metrics for the methods... and so on (if possible :-).

Those are my whishes. But for now it would be very nice if you could 
show me a piece of code that basically kicks off the dependency metrics 
and the counting metrics for a given package. I tried to go through the 
test classes, but it is very hard to get the one at the right level of 
detail.

Many thanks.

	Stefano

Re: [Jmove-users] Status

[Axel T. <ax...@sp...>]

Hi Stefano,

> Hi Christian, Michael and Axel,
> I am looking for a metrics analyzer tool and I came across your 
> project. I would like to use jmove to extract metrics for my 
> sourceforge project (sync4j.sourceforge.net) so I wandered what is the 
> status of jmove.

we will release jmove 0.2 this week - perhaps tomorrow if the new years 
party is not too exhausting ;-).

Release 0.2 is nearly a complete redesign compared to 0.1 with many 
functional extensions. As the release number indicates we are just at 
the beginning of the project and the work has been concentrated on the 
basic functionality.

>  I downloaded the snapshot of the project from CVS and I built it. But 
> now I do not know how to get started. Is it a command line tool? or I 
> have to lunch a GUI?

At the moment jmove mainly provides an API which can be used for byte 
code and source code analysis. We think it is powerful and fairly easy 
to use. jmove analyses byte or source code and creates an model of the 
implementation. The model is defined by the API and is the basis for 
further analysis. So we use it in conjunction with junit to perform 
architecture and design tests. At the moment there are not command line 
or gui tools which produces some kind of architecture or metrics 
report. But i think such tools are not hard to implement and are a 
natural extension of jmove's current functionality.

To use the API you'll require the jmove jar created during the build ( 
build/libs/jmove.jar ).
To get an impression of how to use the API take a look at the classes 
in the org.jmove.examples.java package of the test case classes in the 
*.test packages. One of the next steps will be the improvement of the 
documentation. So long please take a look at our home page 
http://www.jmove.org and especially at our wiki 
http://www.jmove.org/cgi-bin/piki .


> One more question: which metrics are currently implemented?

There are few metrics which jmove currently provides via its API:

- The set of metrics defined by Robert. C. Martin  
(http://www.objectmentor.com/publications/oodmetrc.pdf)

- Lines of Code (only with source code analysis)

- Number of Classes

- Number of Packages

- Number of Members (only with source code analysis at the moment)

Implementing metrics is one of the main goals of the project. So on the 
one hand we will plan to implement more metrics and on the other hand 
we try to make it easy to implement new metrics for jmove 
users/contributers.

I hope this answer will help you a bit. If you have further questions 
just ask. For us it is also interesting to know more about your 
personal requirements. So it would be nice if you let us know what kind 
of metrics or other functionality you would like to find in jmove.


Happy new year

Axel

[Jmove-users] Status

[Stefano F. <ste...@li...>]

Hi Christian, Michael and Axel,
I am looking for a metrics analyzer tool and I came across your project. 
I would like to use jmove to extract metrics for my sourceforge project 
(sync4j.sourceforge.net) so I wandered what is the status of jmove. I 
downloaded the snapshot of the project from CVS and I built it. But now 
I do not know how to get started. Is it a command line tool? or I have 
to lunch a GUI?
One more question: which metrics are currently implemented?

Many thanks and happy new year.

Stefano