-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.SecurityException: class "org.eclipse.jdt.internal.compiler.lookup.LocalVariableBinding"'s signer information does not match signer information of other classes in the same package #148
Comments
I tried using attached project. But did not encounter any problems |
@sravanlakkimsetti did you run the java main? (from eclipse) |
I used maven to build the attached project it got built successfully |
@sravanlakkimsetti the problem is not the build. it is running the class. (run as java application from eclipse) |
Ok I can reproduce the problem. Here is what happened Our signing certificate expired on May 19. We started renewed certificate from then onwards. Actually no idea on how to fix this one. |
yes this looks like a bad timing with the expiry |
does the comparator skip the rsa file&sf files? |
they are skipped during the comparator check. since the jar signed during the build, comparator thinks there is the problem in the newly built jar because of differences in rsa and sf files |
so we would need a way to extract the cert list (using jarsigner verify or the like) and compare them instead |
There is no other fix as to redeploy the three JDT core jars signed by same signer with bumped version, from 4.24 maintenance branch. Whoever consumes any of two jdt jars together via maven will fail at runtime sooner or later, once the classes from same package but from differently signed jars will be tried to load by the JVM. @cdietrich : is this affecting Xtext build/test itself, or you "just" saw it in some other project? |
@iloveeclipse no current Xtext uses old platform cause of Java 8 support, but the Java 17 as source and target branch is affected. Xtend uses jdt compiler under the hood for Java xtend interop I found the problem in our Xtext-maven-plugin integ tests |
any update here |
Also relates to #181 if JDT would using the compiler as a plugin, we might have noticed this earlier... |
@cdietrich if xtext pulls in JDT, it might work to exclude the org.eclipse.jdt.compiler.tool if xtext pulls in tycho... |
we dont know if xtext-maven-plugin runs in tycho env or not. and the problem also happens in pure maven envs |
@sravanlakkimsetti would it be possible to deploy an updated version of the |
We have the same problem. We can not upgrade the target platform to eclipse 2022-06 in our rcp product. |
I (actually, I guess "we") would like to know if on 2022-09 this signing problem will be fixed, please |
i assume this one will never be fixed right? |
Do you mean, 4.25 has same problem again? Could you please provide more details? |
no, i mean there will be no 2.24 fixes |
Sure, for both 2.24 and 4.24 :) |
so i guess this can be closed as wontfix, please update to 2022-09 |
the following main
does fail using jdt 2022-06 maven artifacts
all three artifacts seem to have been published together on june 14th
The text was updated successfully, but these errors were encountered: