To edit or add content to this Wiki, you can simply create a new account at http://wocommunity.org/account.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Create New Directory Structure

Image Modified

The first thing we need to do is to create a new directory structure to allow for multiple versions of WebObjects to be installed in. This new directory structure basically creates a new root level that WOLips will look in for all frameworks used by a given project or workspace. This directory structure can be anything you wish. For demonstration purposes, I'm going to create it under the /Developer directory.

Create: /Developer/WebObjects/Versions/

Download WOInstaller.jar

Image Modified

We now need to download the WOInstaller.jar file from http://webobjects.mdimension.com/wolips/ and save it into the Versions/ directory we just created.

Use WOInstaller.jar to download WebObjects

Image Modified

Open Terminal.app and run one of the following commands:

...

(depending upon which version of WebObjects you would like to download.)

Installed Versions

Image Modified

When the script has finished downloading, your directory should look something like this. At this point you could rename the directory to something like MyCustomer or MyProject. For this demonstration we'll just leave it named as is.

Open Eclipse / WOLips

Image Modified

You need to launch Eclipse and WOLips at least once so that it will create the default wolips.properties file in ~/Library/Application Support/WOLips/. If you've already been using WOlips, you can skip this step.

...

Make a copy of the default wolips.properties file

Image Modified
Select the wolips.properties file and make a copy of it. Then rename the copy to be wolips.yourversion.properties. In reality, you can rename it however you'd like (for example: wolips.properties.533 or 533.wolips.properties), but I find that putting the version number in the middle (e.g. wolips.533.properties) will keep all the different versions together, and will not mess with the extension mapping.

...

Option 1 - Configure the Eclipse workspace to reference your new wolips.properties file

Image Modified

With this option, we're telling the Eclipse/WOLips internal incremental builder to reference a specific wolips.properties file for the entire workspace (rather than using the default, which is $HOME/Library/Application Support/WOLips/wolips.properties). And by doing this, we're implicitly telling Eclipse which installation of WebObjects we want it to use.

...

Note
titleNote

This setting currently affects only the Eclipse internal builder - it will not influence external builds with Ant. That is, when you build your project (e.g. for deployment) using any of the following:

  • Ctrl-click build.xml -> Run As -> Ant Build
  • WOLips Ant Tools -> Install
  • build with Ant from the command line

...this setting will not affect where Ant looks for the various resources specified by the settings in your alternate wolips.properties.

In order to configure Ant so that it can find your wolips.properties-specified resources, you'll need to use Option 2, below.

Option 2 - Configure your project to reference your new wolips.properties file

Image Modified

Currently, the Eclipse Ant builder is not controlled by the "WOLips -> Build" setting in Eclipse's Preferences. In order to build with Ant, you first need to tell Ant where to find your WebObjects installation and other resources. Your project's default Ant buildfile, build.xml (which is created by WOLips when you create a new WebObjects application project), reads and uses the properties found in your $HOME/Library/Application Support/WOLips/wolips.properties file. But you can specify a different wolips.properties file by adding a line like the following to your project's build.properties file:

...