Proper OSGi access restriction warnings for e(fx)clipse maven projects

In the last few days I worked on the last required feature to abandon PDE and use maven (with the bnd-maven-plugin) and m2e.

Does anyone reading my blog know if IntelliJ and Netbeans also have a feature like this?

This entry was posted in e(fx)clipse, Uncategorized. Bookmark the permalink.

4 Responses to Proper OSGi access restriction warnings for e(fx)clipse maven projects

  1. Marcelo says:

    Hi Tom,
    Is there any progress related to this topic?
    Totally unrelated, will Oracle’s new six-month release cadence for Java and the removal of JavaFX affect e(fx)clipse?

    • Tom Schindl says:

      with progress you mean support for those restrictions in Netbeans and/or IntelliJ? e(fx)clipse is not affected by the changes in release speed nor the removal of JavaFX as then it just gets an ordinary dependency for us. We welcome JavaFX getting a real opensource project and will help to push it forwards

      • Marcelo says:

        Thanks for getting back to me. I was thinking of the progress to abandon PDE (to use maven/gradle) but working with Eclipse.

      • Tom Schindl says:

        Progress is good. e4 applications we are developing with out customers are now all build on top of maven!

        Once I managed to include one of the biggest build obstacles is fixed as well.

        Oh and we started converting e(fx)clipse code base to a pure maven build but because of the high (javafx-)workload progress there is slow, for e(fx)clipse it it clearly the way forward.

Leave a Reply

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

You are commenting using your 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.