Skip to Content

Downloading, Building, Installing and Upgrading Wonder Source Code

Version 128.1 by David Avendasora on 2011/04/25 15:18
Warning
For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Introduction

Instead of downloading the Wonder binaries, working from the latest source code directly can have some advantages such as:

  • Learn a lot about WebObjects and EOF (and Java development styles)
  • Easily browse and search the source
  • Work with a specific source control version (teams, quality control, development cycles)
  • Provide opportunities to submit patches for bug fixes or enhancements
  • Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
  • Discover the many Hidden Treasures of Wonder.

Downloading

Error

There is no valid license for Pro Macros. Please visit the Licenses section.

Open a terminal and navigate to a directory where you want to maintain a source "working copy" and just use the following easy-peasy commands to clone Wonder source to your computer.

  1. h5. Clone the source repository from github into a new directory named "WonderSource".
Error

There is no valid license for Pro Macros. Please visit the Licenses section.

git clone git://github.com/projectwonder/wonder.git WonderSource

You should see output something like this:

Unknown macro: noformat. Click on this message for details.

  1. h5. Navigate into the working copy root
cd WonderSource
Error

There is no valid license for Pro Macros. Please visit the Licenses section.

Building

In general, it is recommended that you use Hudson/Jenkins to build your WebObjects frameworks and applications, but it is not required. You can build either from the Terminal as outlined below, or from within Eclipse directly.

Error

There is no valid license for Pro Macros. Please visit the Licenses section.

Error

There is no valid license for Pro Macros. Please visit the Licenses section.

You can build the Wonder frameworks from the source code you just cloned to the default (/Roots) directory with the following command:

Build the frameworks from the "cloned" source.
ant frameworks

Installing

Assuming you already cloned and installed Wonder from source using the method outlined above, you can use the following procedure pull the latest changes into your local repository.

Install the frameworks
sudo ant frameworks.install

This copies the built frameworks from /Roots to the runtime Frameworks directory:

  • Mac OS X: /Library/Framworks/
  • Linux: /Local/Library/Frameworks

You can combine the build and install steps by simply executing this Ant command:

sudo ant frameworks frameworks.install

Upgrading

This will clean out the existing versions of the frameworks. This isn't strictly necessary, you could just re-install over the top of the old frameworks, but deleting then manually copying over the new ones will clean up any old frameworks that are no longer included in the standard build.

  1. h5. Navigate to the original Wonder source directory that you created above during initial source installation
cd /path/to/WonderSource
  1. h5. Pull the changes you do not have and merge them with your local repository
git pull
  1. h5. Build the frameworks.
ant frameworks
  1. h5. Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
cd ~/Roots/
  1. h5. Delete all installed frameworks whose names match the built frameworks in this Roots build folder
for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
Information

If you have any trouble or errors due to your local repository getting hosed, then simply delete the entire local repository directory, the \/Roots directory and just start over using the initial source clone and installation procedure outlined above.

Information

If you have a custom wolips properties file for a specific workspace and you want to have a specific Wonder clone for that workspace, you can simply link your custom wolips properties file to a soft link named build.properties in the working copy root directory. The Wonder build script will supersede all other filesystem layout poperties with the properties in that file.

For example:

{code:none}
cd my/special/purpose/clone/of/Wonder
ln -s /Library/Application\ Support/WOLips/wolips.custom.properties build.properties
{code}

An example of where this approach might be used would be when you have different projects (perhaps in a specially designated workspace) that use a specific version of WebObjects and a specific version or branch of Wonder.

*Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
{code:none}
wo.external.root=/Users/mike/Developer/special/directory/Roots
{code}

*Tip:* A custom WebServer install directory can be specified to Wonder by adding the property 'wo.server.root' to the custom wolips properties file also.