e(fx)clipse 1.0 released

The release

I’m happy to announce the 1.0 release of e(fx)clipse tooling and runtime. I’ve already introduced the most interesting new features in the last 2 weeks

… but there are many many other small improvements, bugfixes, … .

We resolved more the 100 Bug/Feature-Tickets, started to see commercial adoption of our runtime and a vibrant community who started contributing back fixes, filed world class bug reports.

As with any release I’d like to thank some people/organizations:

  • BestSolution.at for sponsoring the development
  • External contributors like Christoph Keimel & Sun Volland for their excellent contributions to the runtime platform
  • the OpenJFX-Team to fix bugs affecting e(fx)clipse and accept contributions so that we could implement missing features

The final bits are in place for you to consume:


I hope you all enjoy the work we’ve done and continue to provide in the next releases to come. Still we could need some help: You might consider sponsoring the project, so that we can provide the services you are used to and provide a reliable tooling & runtime platform you can build your business applications on.

For more information on sponsoring and the packages available take a look at http://efxclipse.bestsolution.at/sponsoring.html or if you need commercial support see http://efxclipse.bestsolution.at/services.html.

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

16 Responses to e(fx)clipse 1.0 released

  1. dlemmermann says:

    Reblogged this on Pixel Perfect and commented:
    Essential tools for any JavaFX developer.

  2. Reto Urfer says:

    i tried to update my Installation but both link
    dont work.
    The link for the runtime p2 repository is working fine.

  3. This is JavaFX 2.2 only, right? Not 8? Or does it even matter since it’s mostly tools?

    • Tom Schindl says:

      the tooling itself requires Java8 as well because we internally make use of lambdas, … but you can of course also target JavaFX2 applications. The OSGi-Runtime layer also depends on JavaFX8 and there we definately don’t support JavaFX2

  4. ncuka says:

    Not being extremely familiar with the terminology, what is the difference betweenthe Tooling and Runtime distributions? For example, if I want to mess around with JavaFX and OSGI (running JavaFX in an OSGI container, building a JavaFX based OSGI bundle) which would be the right update site to use? Thanks for your hard work!

    • Tom Schindl says:

      Most likely you need to both:

      1. The tooling components should be installed into your IDE
      2. The runtime components should be used to define a Target Platform in your IDE. You’ll find a wizard when the tooling is installed to bootstrap a JavaFX/OSGi-Application and or give http://wiki.eclipse.org/Efxclipse/Tutorials/Tutorial4 a spin which use e4 (at least it shows you how to setup a target platform)
  5. Tai says:

    I tried to install e(fx)clipse plugin 1.0 into Eclipse Kepler. However, it complaints dependencies cannot be resolved. Does e(fx)clipse 1.0 only work for Eclipse Luna? Thanks.

  6. Pingback: e(fx)clipse 1.0 veröffentlicht - Java Blog | Javainsel-Blog

  7. I updated 0.9.0 to 1.0.0.
    But I can’t find “org.eclipse.fx.core.fxml.ExtendedFXMLLoader”.
    There is no fxml package in org.eclipse.fx.core_1.0.0.201408150602.jar.
    Where can I get it??

  8. Tomasz Kleszczyński says:

    Repository with efxclipse tooling returns 404. Is it planned or you have some some problems with it?

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.