Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Java Other
Latest commit cb4f39e @darkv darkv Merge pull request #125 from darkv/template_patch
Improve Wonder entity templates

WOLips Icon


With the deprecation of the Apple-supplied WebObjects development tools in the WO5.4 timeframe, WOProject/WOLips has become the recommended toolset for WebObjects development and is the toolset that Apple itself uses internally.

Almost all of the functionality provided by the Apple toolset (XCode, EOModeler, WOBuilder, etc) has been duplicated, greatly expanded upon or re-thought from the ground up in Eclipse and WOLips. WOProject/WOLips is the net effect of thousands of hours of freely-given and paid-for labor by many talented developers, and it is constantly improving.

WOLips Project Home

The home page for the WOLips project is

Installing WOLips

Installing prebuilt versions of WOLips in existing Eclipse installations can be done the same way any other Eclipse plugin is installed.

  1. Add the WOLips update URL to the Available Software Sites list (either through Eclipse > Preferences > Install/Update > Available Software Sites or Help > Install New Software... > Add)
  2. Use the WOLips update URL to install the plugin

Building WOLips


  • Eclipse ( this document is current as of 4.4 Luna)
  • Git
  • JRebel and JProfiler are required if you want to build those parts of WOLips

From the command line...

  1. Checkout source from Github: git clone wolips
  2. Identify path to eclipse for the value of eclipse.home (path to the folder enclosing the eclipse program and configuration directories) Edit ~/Library/ to include the line: eclipse.home=/path/to/your/eclipse (or pass the path in the build command using -Declipse.home=/path/to/your/eclipse)
  3. build with ant. Example:

    user$ ant -Dbuild.version=4.4.0 -Declipse.home=/path/to/eclipse -Dskip.jprofiler=true -Dskip.jrebel=true
  4. verify the build succeeded and the product is in the dist directory

  5. Use the eclipse plugin installation process to install from the dist directory.


Fork of wonder/wolips with changes to develop and debug in Eclipse 4.4 PDE

Installation of WOLips to develop under Eclipse 4.4

Prepare eclipse:

1) Use an extra Eclipse installation to develop and debug WOLips, e.g “Eclipse IDE for Eclipse Committers 4.4.1”

2) Be sure to use Java 1.7 or higher

3) If not already contained in the Eclipse package: m2e : Plugin for Maven - Click the checkbox to the left of "Maven Integration for Eclipse"

4) Google Mechanic -

5) Usefull: JRebel -

6) Usefull: Install JProfile in the new eclipse installation

Prepare WOLips source folder

1) clone to your desktop or fork it in your own repository an clone that

2) If you don't have JRebel installed: Open ../wolips/build.xml and comment all occurrences of “jrebel”

3) If you don't have JProfile installed: Open ../wolips/build.xml and comment all occurrences of “jprofile”

4) Open terminal in WOLips root folder and run ant -Dbuild.version=4.4.0

Prepare workspace:

1) Open eclipse and create a new workspace, e.g. WOLips

2) Create WO_HOME classpath variable under eclipse → Preference → Java → Build Path → Classpath Variabels: eg.: WO_HOME /Library/WebObjects/lib

3) Import woenviroment project

  • Import → General → Existing Projects into Workspace
  • Select ./woenviroment

4) Import wolips projects

  • Import → General → Existing Projects into Workspace
  • Select ./wolips
  • Deselect following entries: EntityModeler eomodeldoc veogen In the case you have not installed JRebel deselect as well ...jrebel and ...jrebel.feature In the case you have not installed JProfile deselect as well ...jprofile.launching and ...jprofil.feature

5) Depending on the Google Mechanic version you had to close org.objetstyle.wolips.mechanic

Debug WOLips

1) Open Debug Configurations Dialog

2) Select Eclipse Application and press new

3) Change Execution environment to Java 1.7 Press Debug

4) In the new instance select your preferred project(s) and start testing and enhancing WOLips

Something went wrong with that request. Please try again.