Strange Error in Eclipse Indigo - java

Has anyone ever seen this kinf of error in Eclipse Indigo?
An internal error occurred during: "Label Job".
Illegal class name "com/sun+jdi/DoubleType" in class file com/sun/jdi/DoubleType
Version: Indigo Service Release 1
Build id: 20110916-0149
I've added a new Schreenshot.
Labebl Job is shown when i click on next step (F6, F8..)
JDI thread evaluation is shown when i drag the mouse on a variable for have informations.
I've never seen this strange error.

Since someone asked me to set an answer in order to mark this question as solved even if someone will probably still have this problem unsolved, but as you can see nobody solved it in different ways (since for the majority there are at least two solutions for problems), so i would mark this answer as best answer:
[My Solution] Delete your Eclipse "installation" and reinstall it to be clean from every errors. Re-install it until the problem is gone (and so there are no installation errors)
If someone is opposed to this answer as best answer, please write it down a real best answer, or make yourself agree with #Drumnbass (that "suggested" me to write the answer) to understand what is right and what is wrong.

I just faced the same issue. I was able to solve the issue by removing all the breakpoints by clicking the double cross button and then restarting the eclipse.

Related

Error running JavaFx 13 on IntelliJ (and yes, thoroughly I have followed the tutorial)

First time with JavaFx. To begin with, I've made sure that my version of Java is, indeed, Java 13: Screenshot:
And, I've followed all the directions on the JavaFx tutorials: https://openjfx.io/openjfx-docs/#introduction
I've spent so many hours on this issue. I found similar problems, but the closest "solution" to my problem assumed that the VM customization was put in verbatim, but I have made sure to use the correct path. I have tried the tutorials for both modular and non-modular applications. I have customized everything, for the project itself to Appearance and Behavior preferences. I downloaded the separate JavaFx 13 file from via Gluon and made sure I was able to access them (I have a Mac, so this required a security override).
I have gone so far as to uninstall all Java and JavaFx libraries from my computer and reinstalled them.
After trying what seems to be everything, I have the same error :(
Screenshot:
Otherwise, if I try to toggle some, I'll get the classic (but dreaded) result:
"Error occurred during initialization of boot layer
java.lang.module.FindException: Module JavaFxProject not found"
Does anybody have some insight into this? I'd love to find out it was a tiny bug that I could easily eliminate, even though I've already spent so many hours trying to solve this problem myself.
Thanks in advance.

Basic Android Project: alternating cannot be resolved or is not a field/R cannot be resolved into a variable errors

I am new to Android Development/Java Programming/Eclipse so please bear with me. I've been going through the Android Developer Training (developer.android.com/training) and the Hello Android book by Ed Burnette and keep running into a problem that is making it difficult to move forward. I'll do my best to describe it and am hoping that the community can help me resolve it.
I began seeing this issue with the Android Developer Training (around Adding the Action Bar -> Adding Action Buttons) and it became impossible to circumvent at Hello Android's 3.3 Creating Opening Screen when I tried adding the Sudoku buttons. The only change I made when going through Hello Android was adding the Android Development Toolkit (ADT) for Eclipse. I don't recall this being a required download going through the Android Developer Training page so I am wondering if its addition could have contributed to the problem.
The issue that I keep running into is that when I go to build the project, Eclipse keeps telling me:
action_settings cannot be resolved or is not a field
activity_sudoku cannot be resolved or is not a field
container cannot be resolved or is not a field
fragment_sudoku cannot be resolved or is not a field
sudoku cannot be resolved or is not a field
I've tried several fixes that I saw on in the forum including deleting the import.android.R from the sudoku.java file in my src folder but that brings up a bunch of errors that say R cannot be resolved into a variable. I've tried cleaning and rebuilding and restarting Eclipse, methods that occasionally worked before Hello Android and the plugin, but keep getting the same errors. I've also tried setting to Android 3.0 and higher thinking that might be an issue but there was no change. Occasionally I get another error regarding not being able to find the path for a container but I've been playing around with the IDE for 15 minutes and can't seem to get it to pop up again.
I could really use some help on this.
Hope to hear from you,
Yusif Nurizade
This solution may, first and foremost, demonastrate how green I am with Android programming but I believe I found the solution.
Initially following the Android Developer Tutorial, I downloaded the latest versions - 18, 19, 20, etc. When I was creating the project, however, I was specifying much early versions for compatibility; all the way down to 7 or 8. I looked into this because I remembered seeing a message from the IDE regarding the Action Bar and how some commands weren't supported on Version X.
I went back and downloaded all the versions down to 7 or 8 and set the compatibility accordingly. The example now works with minimal other changes. I realize that I may be overlooking something but this is the only major change I made and it seems to have done the trick.
Hopefully this will help other newbies!
Yusif Nurizade

Why isn't PlayFramework recompiling my edited .java files properly?

I have been working with the Play! Framework for a few weeks now, and am really enjoying it. Occasionally I have an issue come up which is frustrating me. It starts when I encounter a compile error. I refresh, and see the (excellent) Play! error message. Here's a simple example.
I go to the appropriate file, fix the error, and reload the page. Then I get this compiler error:
Strangely, it shows the updated source code, with the bug fix, but it is throwing the same compiler error from the previous message. If I restart the Play! server, then everything compiles and I can go on as expected, but of course one of the great things about Play! is being able to edit .java source files and see those changes right away in the browser.
Would really appreciate a tip from anyone who's bumped into this before, or has a clue what is causing it! Thanks so much! I am running OSX 10.6.
EDIT
I have also tried manually deleting the tmp/ directory, where the .class files are stored. This does not help, and I get the same behavior, where the edited source code appears, but the old compiler error is still dsiplayed.
My best stab at this is that your clock is screwed up. Do you use time synchronization? Keep a terminal open running:
while true; do sleep 1; date; done
and check whether there is a correlation with clock changes and this behaviour.
FWIW, I've never witnessed this (also on MacOS 10.6)

IntelliJ inspection -- non-thrown exception

This is a follow-up question to 1832203. I'm making it a new question as well, because it seems that posting an answer to a question doesn't change its position on the java page and so I'm worried that it won't get seen. Apologies if I've just stepped on some etiquette toes.
I'm an IntelliJ newbie -- started using it two days ago and I'm absolutely head-over-heels in love! One of the things I adore is the code inspections. However...
In one of my classes I often create exceptions without throwing them. If I can't turn off (or downgrade) the inspection warning for this then I can see I'm going to end up ignoring inspections on at least that file (if not the entire project), which would be a real pity.
I've done a search in the inspection settings for "exception", and found nothing that relates exactly, so I turned them all off just to see, and it's still doing it (even after a rebuild...BTW when are inspections redone? at save? at rebuild? ???), so I would really like some help on how to make this one into an info/typo level -- which I can then ignore.
Using the free version, if that makes any difference
TIA to all those experienced IntelliJ warriors out there!
Press Alt+Enter to show inspection popup, then press Right Arrow to see available options. You'll see there options to suppress this current instance of warning, for this class or completely turn it off.

Eclipse and JavaFX? is it just me?

I'm looking at learning JavaFX.
I've tried setting Eclipse to develop a small app and I've downloaded the Eclipse plugin.
Eclipse JavaFX plugin
BUT... it just seems, well, flakey.
So I have 3 questions...
1: Is there a better plugin?
2: Or is there some great set of tutorials out there that I'm missing?
3: finally, is it meant to be easy to call Java code from FX? I'm stuggling, it there a good example somewhere?
On questions 1 & 2, Eclipse underlines code in red that just shouln't be. For example..
see this image... alt text http://www.qenet.co.uk/fx.jpg
Why does it underline bit of imports in red?
I know this is little of an open ended question. So I guess my main question is this...
Is my experiance of JavaFX and Eclipse the best I can hope for? Or am I missing something ?
(and I'm not looking for a Yes/No response) :-)
Just looking for a discussion on how best to learn/develop JavaFx.
This kind of thing is not unusual. A lot of Eclipse plugin editors have problems dealing with error tags and the like. For example,
I find that the XML and HTML file editors often fail to clear error and warning markers, and the only way to get rid of the markers it is close and reopen the file.
Even the Java viewer gets it wrong in some circumstances, though the problem goes away when the relevant files are saved.
When you update a spelling dictionary, the spelling checker is not rerun and the spelling error markers are not updated. In fact, you have to restart Eclipse for this to happen.
I suggest that you try saving files, and closing/reopening editors to see if that makes the bogus error markers go away. Then decide whether Eclipse is the right IDE for this task.
I've never used NetBeans (at all), but you would expect that it would do a better job supporting JavaFX. After all NetBeans and JavaFX are both high profile Sun products at the moment.
Netbeans is really the only way to go at the moment for JavaFX development. They are both Sun products and Sun has made sure the two work very well together. Before long Eclipse and others will catch up but for the moment that's how it is.
There is another JavaFX plug-in for Eclipse from Exadel. You can download it here: http://exadel.org/javafxplugin. Give it a try.
I have similar problems but funnily only under Linux, not Windows. Hope they change that soon.
To me this has happened when I wronlgy installed javafx sdk 1.2.3....This plugin works only with 1.2.1... :/

Categories