explain in report.tex how many repositories were compiled through Maven/Gradle

yegor256 / cam

Classes and Metriсs (CaM): a dataset of Java classes from public open-source GitHub repositories

http://cam.yegor256.com

MIT License

23 stars 38 forks source link

explain in report.tex how many repositories were compiled through Maven/Gradle #229

Open yegor256 opened 7 months ago

yegor256 commented 7 months ago

Currently, it's not clear why some metrics (like LCOM5 and NHD) are not available for the majority of Java files. Let's explain this in the report.tex and provide statistics -- how many repositories were compiled and how many failed.

Raleksan commented 2 weeks ago

@yegor256

Hi, is this issue relevant at this time? Can I take care about it?

yegor256 commented 2 weeks ago

@Raleksan yes, very relevant, please help

Raleksan commented 3 days ago

@yegor256

Hi, I spent some time to think about this task and not invent adequate solution for it. May you explain in more details that you expect from me:

Just finding repos with Maven/Gradle and note this number in report.
Try to compile them, if success, then collect statistics, else note this in report.

yegor256 commented 3 days ago

@Raleksan when we compile repos in order to calculate jpeek metrics (see metrics/jpeek.sh), we don't record the fact of whether the repo was compiled or not (success or failure). I suggest, we record it somewhere (in some additional file) and then use these files when we build the report in report.sh

Raleksan commented 3 days ago

@yegor256

I investigated metrics/jpeek.sh and found that it just prints hard-coded metrics. Is there another way to collect metrics using jpeek?

I think I need to modify steps/jpeek-repo.sh to handle the repo compilation.

yegor256 commented 2 days ago

@Raleksan you are right, we should modify steps/jpeek-repo.sh. Here, for example, we should not just log the problem but also record this fact somewhere (in some file).