Infinite loop using Standalone

[perelengo]

Hi,
I would like to congratulate the people mantaining this project, it is quite hard to find java reverse tools for java>1.8, I used to use MoDisco but seems abandoned and then discovered this project and I would really like to use it.

I'm trying to reverse a java project with
https://github.com/PalladioSimulator/Palladio-Supporting-EclipseJavaDevelopmentTools/blob/master/bundles/jamopp.standalone/src/jamopp/standalone/JaMoPPStandalone.java

But it seems to enter an infinite loop resolving proxies, because it tries to resolver itself in a loop.

My doubt is if I'm using the correct class, because I guess that the junit tests like
https://github.com/PalladioSimulator/Palladio-Supporting-EclipseJavaDevelopmentTools/blob/master/tests/org.emftext.language.java.test/src/org/emftext/language/java/test/standalone/StandaloneTest.java

Work, but I see there are quite difference between what does the test to parse and what does the standalone class.

Also reading the documentation in the document "Parsing and Printing Java 7-15
by Extending an Existing Metamodel
Martin Armbruster
Supervisor: Manar Mazkatli
July 28, 2022"

I don't understand which class corresponds to the first variant and which to the third.

Could anyone help please?
Kind regards.

[HansMartinA]

Hello,

I am sorry for the late reply and thanks for your interest in using this project.

Unfortunately, the first variant (which is used in your first link of the standalone version) currently does not work because of the infinite loop. As we are currently using the plugins only in Eclipse, we did not use or properly test the standalone version. In the test file (your second link), the third variant is used. Due to the current build pipeline, the test file is also executed in an Eclipse-based environment so that I cannot say if it works in a non-Eclipse environment.

The class for the first variant is the JaMoPPJDTParser while the JaMoPPJDTSingleFileParser class corresponds to the second or third variant based on the settings of the ParserOptions. Per default, the third variant is turned on.

As a side note, we are currently discussing the future plans of this project.