jean pierre Lerbscher

Please provide a test case that reproduces the issue

You have declared a problem in javaparser, it would only be necessary to provide the java code that illustrates the problem. However I have the feeling that it is a...

Thank you for your effort but what is expected is a simple unit test that reproduces the problem (probably about ten lines of code). Be aware, however, that in the...

Since we are talking about unit tests you can copy/paste the test code in the issue. That way I could quickly reproduce your test case without having to install anything.

What is the expected result? A ParseProblemException? I don't think there is a syntax error.

If there is no syntax error which seems to be the case, there is no reason to have a parsing error.

If I dared the comparison I would say that you can perfectly parse code that contains bugs without JP throwing an exception.

I'm not an expert in defining modules in java, but if I understand your comments it's that the syntax is incorrect. What do you think the correct syntax would be?

I'm looking the module declaration on JLS https://docs.oracle.com/javase/specs/jls/se11/html/jls-7.html#jls-ModuleDeclaration and I don't see what is syntactically incorrect in your example. ModuleDirective: requires {RequiresModifier} ModuleName ; exports PackageName [to ModuleName {, ModuleName}]...

I was just reading this part. But the prerequisite for using JP is that the code must compile otherwise you may have unexpected behavior. What I understand from this part...