e(fx)clipse 1.2.0 released

Before going into the weekend and work on my EclipseCon stuff I’m happy to announce the 1.2.0 release of e(fx)clipse tooling and runtime.


e(fx)clipse adds JavaFX tooling to your Eclipse IDE and provides:

  • FXML editor including a live preview
  • CSS editor who knows all JavaFX properties and provides auto-complete and validation
  • (and many many more features)

The tooling is known to work on:

  • Eclipse Luna SR1/2
  • Eclipse Mars M5

You can install the tooling into your IDE using the following p2 repository.

Runtime platform

e(fx)clipse comes with a powerful runtime platform built on top of the Eclipse 4 Application but uses JavaFX for rendering instead of SWT. The e(fx)clipse runtime platform is production ready and used in a number of commerical products.

In case you need SLAs, consulting and commercial support please get in touch with BestSolution.

The runtime artifacts are publised as:

The runtime platform is using Eclipse Luna SR1 as its base and adds many many cool features on top of it. If you are interested in some highlights coming with 1.2.0 release please use this link

Next release 2.0

1.2.0 is the last public release of 1.x series unless something very serious shows up until the next scheduled release 2.0 which will be shipped as part of Mars Release Train.

For customers with service contracts additional releases with backports of bugfixes will be available through BestSolution channels if requested. If you are using e(fx)clipse in your commercial products get in touch with us.

This entry was posted in e(fx)clipse and tagged . Bookmark the permalink.

12 Responses to e(fx)clipse 1.2.0 released

  1. Not Relevant says:

    http://www.eclipse.org/efxclipse/releases.html – The year of the last release should be 2015

  2. Pingback: JavaFX links of the week, February 2 // JavaFX News, Demos and Insight // FX Experience

  3. I am a little bit confused so you may help me out?
    Which latest version of e(fx)clipse does still work with Java 7 and where can I get it?

    Hope you can help me and thanks in advance!

    • Tom Schindl says:

      You need to be more specific – are you talking about the runtime, the tooling? Please also note, while the tooling itself requires you to run your IDE with Java8, you can still develop Java7 applications!

      • Hi Tom,

        yes I was talking about the tooling. I was running Java 8 before and I was able to create JavaFX projects within Eclipse.
        I had to go back to Java 7 and now I can’t do it anymore.
        I thought there is a tool that runs on Java 7 aswell, I think I was wrong, when I understood your answer correctly 🙂

      • Tom Schindl says:

        So why did you have to go back to java7 – We are only talking about the VM you use to launch eclipse, not against what JRE you develop. To answer your question. No there’s no current version of the tooling that runs on Java7 – IIRC the last version that runs on Java7 is 0.9.0.

  4. Pingback: Compensator – A code editor and a code dev environment written in JavaFX | Tomsondev Blog

  5. I had to go back to Java 7 because my companies clients machines are running Java 7.
    I know there is the possibility to create an setup with Inno Setup Compiler, which would create an .exe that installs a part of the JDK/JRE 8 to the clients PC, but the clients can’t install any software…
    Thank you for your answer.

  6. JHeim says:

    I found runtime and tooling incompatible. They can’t be installed side-by-side. (dependencie versions differs). So the sample project can not be build. Any solutions ?

    • Tom Schindl says:

      Thank god they don’t install next to each other. The runtime should only get set as the target-platform why installing that to your IDE?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.