Mac version: OSX Maverick
Eclipse Version: Tried both Mars and the previous Luna release.
Just gotten Eclipse a few days ago and i run across JADclipse, been wanting to look through class files so I went to download it
Spent the past 2 days trying to get it to work, I have done all the steps required:
File Association for jad
Made JADclipse Viewer as Default
Eclipse -clean
Despite that it still gives me the error that
The Class File Viewer cannot handle the given input ('org.eclipse.ui.ide.FileStoreEditorInput').
Can anyone help out?
Full error details
The message is saying that the viewer cannot deal with FileStoreEditorInput. This input is used when you try to open a file which is not in the Eclipse Workspace. So presumably the viewer can only open files which are in the current workspace.
Related
I have recently been using the Atom editor with its ide-java package to do some Java development. It has worked well enough for me and I'd like to continue to use it.
I have just refreshed my Mac from scratch after having some repairs done on it that required erasing the disk. Since installing on this refreshed Mac, I am getting red error highlights on pretty much every line of code, including the first line of files which start with a comment. Most of the errors have a message something like this:
The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
A Google search shows this error and some fixes within Eclipse projects, but I am not (directly) using Eclipse and I've had a hard time figuring out how to fix the problem in ide-java.
I've tried deleting the .project file and the .settings folder and allowed them to be auto-regenerated. I've tried uninstalling and re-installing the ide-java package. I've tried setting the package's Java Home to both a Java 8 and a Java 10 home folder. None of these have made a difference.
Can anyone offer any advice on how to troubleshoot and make this work as it has for me in the past?
To fix this - you can try to reset atom settings.
For linux:
mv ~/.atom ~/.atom.bak
You will have to install packages again, but this helped me to fix the issue
I have pyDev installed on Eclipse, but I quit the eclipse without saving python module yesterday. The Eclipse got crashed when I tried to open it. So I download the eclipse and install again. The new one can open java project and class, but for python, it said that: Could not create the view: org.python.pydev.navigator.view
No editor descriptor for id org.python.pydev.editor.PythonEditor
What can I do now? I didn't find anything useful till now.
I've got some class files that open in Netbeans (with .java extension) but in Eclipse I had the following experience:
At first I could not see the content of the class files with jadclipse and I only saw:
/jadclipse/
//Error!
A few days later (without any change to eclipse or ...) I could see them but with errors like the ones bellow:
"Couldn't fully decompile method ...
Couldn't resolve all exception handlers in method ...
Overlapped try statements detected. Not all exception handlers will be resolved in the method ..."
But the other day I ran into the first error that I could not see anything again!!!
OS: Win7
Java: 7
Netbeans 7.1.2
Eclipse version Juno Service Release 1
Any suggestion?
I didn't get any help on Eclipse plugin of JAD as I said it didn't work for my class files. So I tried Java Decompiler GUI and it worked very nice, therefore I wanted to share this nice experience so that it might be useful for some body.
Windows xp sp3
Eclipse Junu with CDT
I've been trying to debug a JNI project using the process attachment feature.
At first, I fire the Java program, and then, when I fire the C program, I suppose to choose the javaw.exe process.
The tutorial I used for JNI debugging
The problam is, when I suppose to choose the right process, the process list seem to be empty:
Here is my debug configuration:
What can I do? Should I replace the debugger?
Thanks in advance,
Mark.
I encountered this problem using eclipse CDT plugin in Eclipse Juno on windows. Using sysinternals process monitor I discovered that eclipse was looking for a class file:
C:\Program Files\eclipse\plugins\org.eclipse.cdt.core.win32.x86_64_5.2.0.201209170703\org\eclipse\cdt\internal\core\win32\ProcessList.class
but not finding it (Eclipse is installed on my system in C:\Program Files\eclipse). The missing class file is present in the jar file:
C:\Program Files\eclipse\plugins\org.eclipse.cdt.core.win32_5.3.0.201209170703.jar
I am not sure why eclipse can't find the file in the jar. I copied the entire "org" directory tree out of the org.eclipse.cdt.core.win32_5.3.0.201209170703 jar into the file system. Having done that, eclipse can now find the file
C:\Program Files\eclipse\plugins\org.eclipse.cdt.core.win32.x86_64_5.2.0.201209170703\org\eclipse\cdt\internal\core\win32\ProcessList.class
(and other files in that jar) and the process pick list is now populated.
This didn't work for me. I was able to find the jar and extract the jar, but still got the same error.
I switch back to Eclipse v3.7 (Indigo) with CDT and everything works. Same GCC toolchain and project, all I did was change which version of eclipse I was using and the attach to process works fine. I'll report the bug to CDT team but Juno is really costing me some man hours (both for CPP and Java...)
Good luck other CDT users!
UPDATE:
I was able to get your workaround to work. I extracted the specified jar and it came out as a 'org' directory in the plugin folder. But really, it needed to be extracted in the directory/folder that has the same name as the Jar. This is strange...
Well, Juno+CDT is working again.. guess I shouldn't be such a hater ;-)
Getting this strange error in Eclipse (Helios). I can't show the package explorer.
Could not create the view:
org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/ToStringGenerationSettings
(wrong name:
org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/ToStringGenerationSettings$CustomBuilderSettings)
Same error when trying to open a java class file. Any clues?
Agreed with Arne's and Gilbert's comments. If this is still an issue, a few things you can try to resolve:
Try a new workspace (using the same Eclipse installation).
Trying a new Eclipse installation (using your same workspace). This would also be a good chance to upgrade to the latest version of Eclipse, now 3.7 / Indigo.
(Primarily posting this answer in an attempt to either get this question some additional attention / competitive answers, or at the least, to simply remove this from the growing list of unanswered questions.)