mariazevedo88 / o3smeasures-tool Goto Github PK

In addition to the options to export the measurement file (.csv or .xml) to the local device, create an option to export them to an AWS (Amazon Cloud) S3 bucket.

Show if the measurements are below, average or above the reference values suggested in the literature/specialists.

Create the automation workflow of the project in Github Actions.

The calculation of the Number of Children measure is considering the relationship implements and should not.

It would be great if you can export every data in the results and not only the summarized/collapsed view.

The Cyclomatic Complexity calculation is not considering MethodInvocation expressions.

A plugin bug was noticed after email feedback requesting help in understanding the evaluation of multiple projects.

The plugin was designed to evaluate only one project at time, but was allowing multiple projects to be selected.

I've installed Eclipse 2020-09 and used the Marketplace client to install O3SMeasures. I opened a workspace that has some projects from various Git repos. I opened the 5 views in Window > Show Views > Other... > o3smeasures. When I right click a Java based project, there is no "O3SMeasures -> Analyze Java project" on the context menu. How do I analyze my code? There's nothing that shows up in the workspace's .log file that relevant; only some key binding stuff.

!SESSION 2020-12-01 11:38:49.326 -----------------------------------------------
eclipse.buildId=4.17.0.I20200902-1800
java.version=11.0.8
java.vendor=Red Hat, Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product

It is great the ability to measure and have all the metrics directly in Eclipse IDE. Anyway, it would be great if you can have the results without the graphic interface, so you can use this measures as part of, for example, a Continuous Integration (CI) pipeline or execute it for a group of projects in an unattended way.

The LackCohesionMethodsTwo calculation it's wrong. The correct formula is:

(avg(m(a)) - m)/(1 - m)

Os testes unitários do projeto atualmente estão desenvolvidos com JUnit4. Atualizar o framework para a versão 5.

The WeightMethodsPerClass calculation is not considering MethodInvocation, Finally blocks and Java 8 expressions, such as Lambda and Method Reference.

Adjust project's configuration so that it can be run from at least Eclipse Oxygen to the latest Eclipse release