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
SuccessNow with more Git
As of March 25th, 2011 the Wonder source code is now maintained on [GitHub|https://github.com/] at [https://github.com/projectwonder]. So you'll need to be familiar with the [Git|http://git-scm.com/] Source Code Management system. You will use it to checkout a local copy of the repository (a "clone" in Git terms) allowing you to have direct access to the Wonder source.
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.
- h5. Clone the source repository from github into a new directory named "WonderSource".
WarningRead Only
Note the URL shown here is the public read-only URL. Committers should use the SSH form of the URL for read-write
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.
The [noformat] macro is not in the list of registered macros. Verify the spelling or contact your administrator.
- h5. Navigate into the working copy root
WarningWebObjects 5.3.3 Compatability
If you are still using old WebObjects 5.3.3, then you need to execute this git command to switch to the branch for WebObjects 5.3.3: {code}git checkout track origin/Wonder_5_0_0_Legacy{code}
You should get output like this:
{noformat}
Branch Wonder_5_0_0_Legacy set up to track remote branch Wonder_5_0_0_Legacy from origin.
Switched to a new branch 'Wonder_5_0_0_Legacy'
{noformat}
Building
In general, it is recommended that you use Hudson/Jenkins to build your WebObjects applications, but it is not required. You can build either from the Terminal as outlined below, or from within Eclipse.
SuccessPro Tip
If you use Hudson/Jenkins to build your WebObjects applications, then you do not need to actually build or install the Project Wonder frameworks on your development machine, just having the individual Wonder source code projects open in your eclipse workspace is sufficient.
WarningRequires WebObjects
These build instructions require the WebObjects frameworks to already be installed in the normal location:
- Mac OS X: {{/System/Library/Framworks/}}
- Linux: {{/Library/Frameworks}}
Otherwise you will get compiler errors like this:
{noformat}
[wocompile] /Wonder/WonderGit/WonderSource/Frameworks/Core/JavaWOExtensions/Sources/com/webobjects/woextensions/JSAlertPanel.java:10:
package com.webobjects.appserver does not exist
[wocompile] import com.webobjects.appserver.WOContext;
{noformat}
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.
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.
- h5. Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
- 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
- h5. Navigate to the original Wonder source directory that you created above during initial source installation
- h5. Pull the changes you do not have and merge them with your local repository
InformationIf 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.
InformationIf 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.
