THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Warning | ||
|---|---|---|
| ||
Before any interaction with OFBiz in Eclipse be sure to run "gradlew eclipse". This generate the information Eclipse needs about the OFBiz project. |
...
- CTRL+SHIFT+R for finding resources!
- CTRL+H for finding text in files
- The rest you will find on Internet
Note: though it's now more history, for me at least, here is what I got through initially when working with Gradle in Eclipse
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
Setting up Eclipse to work with OFBiz is easy.
There are two ways to import OFBiz into Eclipse:
- You can either allow Eclipse to download OFBiz directly from SVN,
- or you can import an already downloaded copy of OFBiz (from SVN or otherwise) from the filesystem.
...
| title | Mostly for committers but also for users who mind about svn history and annotations. |
|---|
...
- .
...
...
...
Importing OFBiz from the filesystem into Eclipse
If you have already downloaded OFBiz and do not wish to have Eclipse handle SVN pulls for you, Eclipse can import OFBiz from the filesystem as well.
...
- Right-click in the Navigator window and click on Import.
- Select "Existing Project into Workspace" and click Next.
- Click Browse and select the directory that contains the ".project" file, then click Finish. When this is complete, a new project named "ofbiz" will now appear in your Navigator. This will not copy the project to Eclipse's workspace directory: it will remain wherever it was before the import. If you want the OFBiz files in your workspace directory, you must move them there before you do the import. Note that by doing so you will not have the the plugins inside your ofbiz project. If you want that, follow the info in the "Setting up Eclipse to work with OFBiz is easy" section above.
...
Using SVN from within Eclipse
If you want to do the SVN pull from within Eclipse, use the following steps:
- First you need to install Subclipse
- Bring up the "SVN Repository" panel in Eclipse (Window/Open Perspective/SVN Repository Exploring)
- Right-Click within panel/New/Repository Location
Pick the URL of the one you are interested in at http://svn.apache.org/repos/asf/ofbiz/
eg: http://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk/ - Click on Finish. Now, do the initial checkout.
- Click the "+" next to the new repository
- then Right-Click on trunk and select "Checkout...".
- Select "Check out as project in the workspace" and click on "Finish".
- This will create a new project that you can name as you want and download the OFBiz files directly from SVN. To sync your project with SVN in the future, right-click on the project and click Teams/Synchronize with Repository. Note that by doing so you will not have the the plugins inside your ofbiz project. If you want that, follow the info in the "Setting up Eclipse to work with OFBiz is easy" section above. Then of course import the project from the plugins directory inside the OFBiz project.
...
Using GIT from within Eclipse
You will need "Git Team Provider" package (integral part of many Eclipse IDE builds) for this to work. If not installed please check "EGit - Git integration for Eclipse".
...
For more information about how to manage the repository please see EGit/User Guide - Managing Repositories.
Eclipse and Gradle
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 | ||
|---|---|---|
| ||
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.
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 
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.