Versions Compared

Old Version 63

changes.mady.by.user Jacques Le Roux

Saved on

compared with

New Version Current

changes.mady.by.user Jacques Le Roux

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Title: hide (not add) some files when opening a file.

...

For more information about how to manage the repository please see EGit/User Guide - Managing Repositories.

Eclipse and Gradle

The best There are several Eclipse plugins for Gradle. In our experience they don't all provide the same level of features and quality. A good Eclipse plugin for Gradle is "Pivotal EGradle IDE" you can find it with MarketPlace and it offers almost all what you need.

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. Install the best Eclipse plugin for Gradle: "Pivotal EGradle IDE". You can find it with MarketPlace and it offers almost all what you need.
  2. "Customize your Perspective" to show the EGradle buttons in the toolbar
  3. Run pullAllPluginsSource inside Eclipse using the "EGradle quick launch" feature (use the button in the toolbar).
    Beware if you have pending changes they will be lost. So if you have already done the 6 steps here, you might prefer to update using svn...
  4. Import the just checked out the plugins project in Eclipse.
  5. Follow https://stackoverflow.com/questions/9163501/eclipse-import-folder-of-source-code-to-other-projects.
  6. You should now be able to use the ofbiz project to handle both framework and plugins (in a sub-project).

There is only one drawback. I you run "gradlew eclipse" (notably needed after a cleanAll), you need to redo the 3rd step.

...

Hide folders from searches and hide some files when opening a file.

Most of the time you don't want to look into some folders because there is nothing interesting there and they sometimes annoy you because of search errors (sad)

It's also annoying to see *.class files when you look for a similar Java source.

Then you tool of choice is https://nodj.github.io/AutoDeriv/

...

# sets these folders as derived
*.gradle
.settings
bin
build
gradle
lib
runtime/indexes
runtime/catalina
runtime/data
runtime/logs/birt
runtime/output
runtime/tempfiles
runtime/tmp
runtime/uploads

...

A new file .catalog.xml has been introduced in OFBiz root starting from svn 1326499. This file contains a definition compliant with the Oasis Catalog specification of all schemas used by ofbiz. You can import it in you Eclipse workbench by following the explanation at the Eclipse Import XML catalog section (hint: use the Eclipse Import/XML feature). Note also that the platform:/resource notation is used to identify a resource located in the workspace. The next path segment after "resource" should be the name of a project, which can be followed by the folder and/or file we want to locate. So you might need to change the workspase name part of the path according to your real project name.

Here is an example

 

Eclipse and Gradle

The best Eclipse plugin for Gradle is "Pivotal EGradle IDE" you can find it with MarketPlace and it offers almost all what you need.