You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not really sure if this is really an issue. I have managed to create a jar of a bunch of classes. Some of these classes are proxy classes that have fully qualified names of style "com.sun.proxy.$Proxy1" and "com.sun.proxy.$Proxy2" and so on. Now when this JAR is put on the classpath of one of my eclipse projects, I am able to examine the non-proxy classes, but all proxy classes are missing (though the package com.sun.proxy shows up). Is there some check that doesn't allow classes that begin with weird symbols, like $ to show up?
I confirmed the presence of the classes by looking at the contents of the jar
As a final workaround, I pasted one of the classes into the target folder of the project and tried to view its decompiled output - but it was not able to decompile. I am using 0.1.3 of JD-Eclipse plugin.
Any help would be greatly appreciated - thanks!
The text was updated successfully, but these errors were encountered:
I am not really sure if this is really an issue. I have managed to create a jar of a bunch of classes. Some of these classes are proxy classes that have fully qualified names of style "com.sun.proxy.$Proxy1" and "com.sun.proxy.$Proxy2" and so on. Now when this JAR is put on the classpath of one of my eclipse projects, I am able to examine the non-proxy classes, but all proxy classes are missing (though the package com.sun.proxy shows up). Is there some check that doesn't allow classes that begin with weird symbols, like $ to show up?
I confirmed the presence of the classes by looking at the contents of the jar
As a final workaround, I pasted one of the classes into the target folder of the project and tried to view its decompiled output - but it was not able to decompile. I am using 0.1.3 of JD-Eclipse plugin.
Any help would be greatly appreciated - thanks!
The text was updated successfully, but these errors were encountered: