Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Improves info for Subclipse

...

Info
titleMostly for committers but also for users who mind about svn history and annotations.

OFBiz has been split between framework and plugins. It's though still possible for Eclipse to handle the plugins inside the framework by embedding the ofbiz-plugins project inside the ofbiz (ofbiz-framework) project. That's interesting notably if you use Subclipse.

  1. Run "gradlew pullAllPluginsSource"  from ofbiz-framework project root.
  2. Import the just checked out ofbiz-plugins project in Eclipse.
  3. Follow https://stackoverflow.com/questions/9163501/eclipse-import-folder-of-source-code-to-other-projects.
  4. You can may then close ofbiz-plugins project , you should (better keep it open see below). You should now be able to now use the sole ofbiz project ofbiz to handle both framework and plugins.

I have though found it can be erratic, but most of the time it works. There is only 1 drawback. If you run gradlew eclipse your ofbiz project will lose the relation with its ofbiz-plugins sub project because this Gradle task delete and create a new .classpath files which destroy the relation created when following the stackoverflow answer. Then you need to make the steps above again. It's maybe the reason why it can be erratic. Note that you only need that if you wan to use Subclipse for plugins from inside the ofbiz (ofbiz-framework) project. Else the plugins project should still stay open and you can use Subclipse there. We can maybe automate that with Gradle but I'm not sure how.

...