I’ve just updated the All-In-One downloads to Luna M7 and there are multiple reasons you should care:
- General improvements and bugfixes
- JDT Java8 improvements
- JDT understand JavaFX-Properties-JavaDoc
For those of you writing JavaFX applications and wondered why no JavaDoc was shown when they hovered e.g. Stage#setOnCloseRequest(), getOnCloseRequest() and onCloseRequest() should take a look at the source code
You notice – NO JavaDoc on the get & set method – strange because the HTML-JavaDoc has them documented
Starting with M7 JDT understands this pattern
Unfortunately the JavaFX team uses the pattern in an inconsistent way so the JavaDoc does not work in all situations. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=434269
Tomsondev Blog 
I frequently update my eclipse fx to the latest nightly build, but some time ago the integrated CSS and FXML editors stopped working. If I open a *.css or a *.fxml file the system default editor is opened instead..
And I can not configure eclipse to use the internal CSS/FXML editor again, because they are not listed.
Sadly this behavior still exists in the current M7 build?
Are you running your IDE with Java8? If not then this is the reason it does not work anymore! Even worse was that in M6 if you have not been running from the initial install with Java8 those bundles would not have been resolved at all at anytime (bug in equinox) – I guess I’ll better add a warning that pops up informing about the problem when running with Java7.
That did the trick, thanks for the quick hint!
Perfect – https://bugs.eclipse.org/bugs/show_bug.cgi?id=434280 will now warn you if you missed to run with Java8!
Pingback: e(fx)clipse – All-in-one updated to Luna RC1 | Tomsondev Blog