26 Jul
2012
26 Jul
'12
7:29 p.m.
On Jul 25, 2012, at 3:59 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote:
---
Jannik Laval
On Jul 24, 2012, at 9:33 PM, jannik.laval wrote:
Ok, all the MSE files are generated, I have them.
I will share them.
For the metadata, I propose to use an xml file that is independent of mse files / source
files.
why xml?
We could use use as use as well. It is usually much more readable than xml.
iep,
Just that xml is verbose :)
But mse is good too.
Jannik
- keeping source code (and much more) is
important because you never know what people would like to do in the future.
It happened to a team in Brazil recently, they correlated some metrics to bugs.
So they needed on top of the MSEs: access to a bug-tracking system to identify
bug-identifiers; access to SVN commit comments to identify bug-fixing commits; access to
the code to know what methods/classes were changed to correct the bug.
Anyway, people want to see source code. If something looks strange in a visualization,
you want to go back to the code to understand what's happening.
Since qualitascorpus.com already provides and maintains a good collection of java
projects, we thought about reusing that valuable source of information and building the
MSE repository as a complement to Qualitas Corpus.
This means that MSE files would be generated and hosted by us and source code can be
downloaded from qualitascorpus.com.
It could contains all the informations that we
discussed here.
Jannik
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Andrea
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---
Jannik Laval
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev