Call hierarchy broken in Eclipse/STS since FS 2024.11
Hey folks,
who else is a dino and uses Eclipse or STS? We found the call hierarchy shows empty when there is at least one FS type in the parameter list or return type of the method. Until FS 2024.10 it's ok, beginning with 2024.11 every FS jar (fs-isolated-client, fs-isolated-webrt and fs-isolated-runtime) causes this problem with Maven and Gradle. When using Eclipse Java project alone it works, but who wants to do this?
Did somebody observe the same and can confirm this behavior?
Cheers, Heiko
-
There is a bug in Eclipse older than version 4.27. Which version are you using?
0 -
Latest STS based on latest Eclipse
0 -
It seems the the bug in Eclipse has resurfaced. My advice is to report this issue so it can be fixed for good in the IDE.
0 -
Maybe it was not completely fixed in Eclipse, because for plain Eclipse Java projects the problem does not exist, only for Maven and Gradle projects. But can I be sure, that one or many of you guys can confirm this issue?
And btw: in the Eclipse ticket they say: "The dependency we are referencing contains a
module-info.classthat is invalid" and I claim this is also true for the FS jars: they contain invalid module-info.class, so this is a bug in FS in packaging the jars.I invented a hack/workaround: we remove the invalid module-info.class file from the jars before we upload it to our Artifactory
0 -
You are correct, the module-info.class is a result of the shading process and should not be included. We created an internal ticket for that.
Nevertheless, that file has no impact on the functionality of the runtime jar or its interpretation by the JRE/JDK, so I still vote for bringing this to the attention of the Eclipse developers.
0
Please sign in to leave a comment.
Comments
5 comments