I am working on Eclipse IDE for Java (Indigo). My project is using CDT in addition to Java source. I frequently get this error message from Eclipse, although everything works fine.
What is C/C++ indexer? What is the actual source of this error and how to remove it?
The C/C++ indexer parses your source code file to gather information used for auto completion, syntax highlight and so on.
You said you are using CDT in addition to Java source. Sounds to me as if you are using C/C++ and Java code in the same Eclipse Project. My guess would be that the C/C++ indexer accidentally tries to parse a Java source file and is confused. If so, use different Eclipse projects for your Java and for your C/C++ code.
Related
I give a computer programming course I have written, and I recently switched to recommending Visual Studio Code in the course. We are starting out with the basics, so I just wanted a simple editor. We started learning Git, and one student's repository suddenly had all sorts of cruft in it, including:
.settings/
.vscode/
.classpath
.project
In particular the .settings directory had all sorts of Eclipse settings, such as I would expect to see in an Eclipse project.
The student explained to me that these came from VS Code after installing its Java extensions. But why are the VS Code Java extensions creating Eclipse files? And where is all this documented, so that I can update my lessons with the exact details and avoid this problem in the future?
Thanks in advance.
Simplified the Language Support for Java™ by Red Hat is the headless Eclipse Java IDE integrated into Visual Studio Code via the Language Server Protocol (LSP). See the self-description of the extension:
Provides Java™ language support via Eclipse JDT Language Server, which
utilizes Eclipse JDT, M2Eclipse and Buildship.
Except for .vscode/, the mentioned files are Eclipse Java IDE files.
Because in Eclipse these files are not intended to be edited manually, there is little or no documentation about them (the Java compiler settings in .settings/org.eclipse.jdt.core.prefs are similar to the command line arguments of the Eclipse batch compiler).
For example, the documentation of the Java extension recommends using the Eclipse Java IDE to edit the formatter settings (which are also stored in .settings/org.eclipse.jdt.core.prefs) and concludes:
No it's not an ideal solution, but it should be done only once, unless
you regularly change your formatter settings.
I'm using ImageJ for image processing for a class, and I've been creating small plugins for a few weeks. It's been frustrating for me because I never saw any java error messages, such as syntax error on line 3 blah blah. When my plugins don't compile (due to some compile time error), all I see is "class not found", or if a plugin had compiled in the past and there is a class file available it will run the old compiled version and not give me any error.
I thought this was normal until I met up with my friend and he had been getting error messages the whole time.
Any idea why this is? I'm using windows (tried on windows 10, 8, and 7), he's using some osx distribution (most likely the latest). I've tried all available versions of ImageJ from the website, so I don't think it's a version issue. Is this the norm on windows for some reason?
I suspect you are using ImageJ 1.x, e.g. downloaded from here? And trying to compile via Plugins>Compile and Run...?
In general, I would recommend developing Java code in Eclipse - as having a proper IDE is vastly more powerful than what you can get in ImageJ.
If all you need to do is write simple Macros calling existing ImageJ functions then writing them in the various non-Java scripting languages within ImageJ is perfectly sufficient.
If you decide Eclipse isn't your thing and you want to continue developing within ImageJ, I would strongly recommend using the Fiji distribution of ImageJ - as it includes a robust script editor.
If you use this editor to write Java code, it will save your scripts to disk as .java files and then call the Java compiler (javac) on them, which will give you a more complete picture of any compilation problems.
I've been looking into scala lately and from the conciseness and language features I'm completely thrilled.
I have netbeans 8.0 running on ubuntu 12.04 and downloaded scala, edited netbeans.conf (netbeans_default_options="-J-Dscala.home=...), installed plugins from plugin manager inside netbeans (ALL OF THEM). Then, I created scala project (not maven one) and tried out autocomplete. It works, compiles, runs, however, it shows no document found in autocompletion.
This is how I added javadocs Tools > Scala platforms > javadoc tab
I tried adding following ways:
added the entire scala api doc zip from http://downloads.typesafe.com/scala/2.11.2/scala-docs-2.11.2.zip
extracted the previous zip to scala-home folder under $SCALA_HOME/docs/javadocs/scala-docs-2.11.2 and added that
same as 2 but added $SCALA_HOME/docs/javadocs/scala-docs-2.11.2/api in netbeans
None of these pick up documentation! Of course, I could live without it, but it's such a killer for such a concise language where I could just find out stuff instantly from autocompletion. Also, I don't want to use eclipse special ide for scala because I don't want to throw out all the experience with netbeans out of the window and learn new IDE.
P.S. - Netbeans navigator also seem not to work in scala.
And I wonder why there's so little content on google for such a wonderful language?
There is no need to change to IntelliJ. Use the right build tool -sbt or Maven- and everything works fine.
In Netbeans you can use e.g. free Application Servers.
Netbeans support for scala seems pathetic so I just decided to jump to IntelliJ IDEA. It was little bit of learning curve but I'm glad I did because now everything was working (autocomplete, documentation, awesome SBT support etc. etc.)
I read some tutorials about making Eclipse plugins, but every text was just about Java coding. Does it really have to be Java or there is some way to write a plugin in some other JVM language such as Scala or Clojure?
You can use all languages that are based on JVM. You need to simply add a dependency jar (e.g. Scala dependency).
Tested live, so it must work!
Current version of Scala IDE is written in Scala
I am using JPL, a JNI library for interacting with Prolog from Java. In my application it is important to see the output that the Prolog engine generates (for example: when loading Prolog files, executing unit tests, etc). This is happening when I use the library in a standalone Java application.
However, when I pack my application as an Eclipse plug-in, I cannot see the JPL generated output anymore (such output is coming from the Prolog engine).
Does someone know if there is a way to see this output in the Eclipse console?
Thanks in advance.
May be you could try to make a plugin out of your library (hwoto) and then hook a LogListener for this plugin (like that)?