There was only one such place in the code, so the problem was easily fixed. Based on information in the book Eclipse, Building Commercial-Quality Plug-ins, I knew I had to look for IMarker. I figured it would be easy to fix the issue where compilation errors use up three lines in the Problems view, so that’s where I started.

With the build working it was time to tackle one of the problems I encountered during my usage of the plug-in. With these three modifications I could finally issue a build with just a simple ant. I introduced a JAVAFX_HOME environment variable to store that location. The same goes for the location of the JavaFX SDK. So I patched the build to get this location from the environment variable ECLIPSE_HOME which I set in my. For instance I needed to specify -DeclipseDir=/opt/eclipse every time. Next, it bothered me that I needed to provide several properties on the command line. The first thing I ran into, is that the default target didn’t exist. I followed the steps described in the Wiki to get the project compiled. So I decided to do just that, and checked out the code from the Subversion repository. Therefore, the source is available, and anyone can fix problems and supply patches. Luckily, the plugin is released under an Open Source license ( BSD).

A while ago I wrote about how the JavaFX Eclipse plugin has some shortcomings.

Javafx sdk download for eclipse