Skip to Content
Version 172.1 by Kieran Kelleher on 2010/10/04 21:09
Hide last authors
Kieran Kelleher 136.1 1 == Introduction ==
David Avendasora 128.1 2
Kieran Kelleher 136.1 3 Instead of downloading the Wonder binaries, working from the latest source code directly can have some advantages such as:
miguel77mex 77.1 4
Kieran Kelleher 170.1 5 * Learn very much about WebObjects and EOF (and java dev styles?)
6 * Easily browse and search the source
7 * Work with a specific svn version (teams, quality control, development cycles)
8 * Provide opportunities to submit patches for bug fixes or enhancements
David Avendasora 112.1 9 * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
Kieran Kelleher 170.1 10 * Discover the many Hidden Treasures of Wonder
David Avendasora 112.1 11
Kieran Kelleher 170.1 12 == Source Frameworks Initial Installation ==
David Avendasora 112.1 13
Kieran Kelleher 172.1 14 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 download the Wonder source. Note that as of repository version 11387 (Sep 27, 2010) the Wonder repository URL is the only difference between the Wonder source procedure for WebObjects 5.3.3 and WebObjects 5.4.3 installation. For your copy/paste convenience, the full procedures for both WebObjects 5.4.X and 5.3.X are shown below. WebObjects 5.4.3 and the Wonder branch for same is recommended and is where the most features are expected to be found.
miguel77mex 77.1 15
Kieran Kelleher 172.1 16 {{code title="Procedure for WebObjects 5.4.X"}}
miguel77mex 77.1 17
Kieran Kelleher 172.1 18 # Checkout the source from subversion repository into a new directory named "WonderSource"
19 # Note instead of HEAD, you can use a specific svn version number if you want
20 svn co http://wonder.svn.sourceforge.net/svnroot/wonder/branches/Wonder_5_0_0_WebObjects_5_4_Branch/Wonder --revision HEAD WonderSource
David Avendasora 128.1 21
Kieran Kelleher 172.1 22 # Navigate into the working copy root
23 cd WonderSource
miguel77mex 77.1 24
Kieran Kelleher 172.1 25 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
26 ant frameworks
27
28 # Install the frameworks (this just copies the built frameworks from ~/Roots to
29 # the runtime Frameworks directory, usually at /Library/Frameworks)
30 sudo ant frameworks.install
31
32 {{/code}}
33
34 {{code title="Procedure for WebObjects 5.3.X"}}
35
36 # Checkout the source from subversion repository into a new directory named "WonderSource"
37 # Note instead of HEAD, you can use a specific svn version number if you want
38 svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision HEAD WonderSource
39
Kieran Kelleher 170.1 40 # Navigate into the working copy root
41 cd WonderSource
David Avendasora 128.1 42
Kieran Kelleher 172.1 43 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
Kieran Kelleher 170.1 44 ant frameworks
45
46 # Install the frameworks (this just copies the built frameworks from ~/Roots to
47 # the runtime Frameworks directory, usually at /Library/Frameworks)
48 sudo ant frameworks.install
49
50 {{/code}}
51
52 == Source Frameworks Upgrade Installation ==
53
Kieran Kelleher 172.1 54 Assuming you already installed Wonder from source using the method outlined above, and you are using the branch of Wonder appropriate to your WebObjects version, you can use the following procedure to upgrade to a newer, or just different version, as long as that version is greater than repository version 11387 (Sep 27, 2010, which was when the WO 5.4 branch was first introduced).
Kieran Kelleher 170.1 55
Kieran Kelleher 172.1 56 {{code title="Procedure for WebObjects 5.3.X or 5.4.X"}}
Kieran Kelleher 170.1 57
58 # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
59 cd ~/Roots/
60
61 # Delete all installed frameworks whose names match the built frameworks in this Roots build folder
62 for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
63
64 # Navigate to the original Wonder source directory that you created above during initial source installation
Kieran Kelleher 142.1 65 cd /path/to/WonderSource
66
Kieran Kelleher 172.1 67 # Update the source to the HEAD revision (aka latest). You can also use a specific svn
68 # repository version instead of the term 'HEAD', for example 11272
69 svn update --force --accept theirs-full --revision HEAD
Kieran Kelleher 142.1 70
Kieran Kelleher 170.1 71 # Clean, build and install the frameworks
72 ant clean; ant frameworks; sudo ant frameworks.install
Kieran Kelleher 142.1 73
Kieran Kelleher 170.1 74 {{/code}}
Kieran Kelleher 156.1 75
Kieran Kelleher 170.1 76 {{info}}
tmk 168.1 77
Kieran Kelleher 172.1 78 If you have any trouble or errors due to your working copy getting hosed, then simply delete the entire working copy directory, the \~/Roots directory and just start over using the initial source installation procedure outlined above.
Kieran Kelleher 142.1 79
Kieran Kelleher 170.1 80 {{/info}}
Kieran Kelleher 142.1 81
Kieran Kelleher 170.1 82 {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}}
Kieran Kelleher 142.1 83
Kieran Kelleher 172.1 84 If you have a custom wolips properties file for a specific workspace and you want to have a specific Wonder source working copy 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.
Kieran Kelleher 170.1 85
86 For example:
87
88 {code}
Kieran Kelleher 172.1 89 $ cd my/special/purpose/working/copy/of/Wonder
Kieran Kelleher 170.1 90 $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
91 {code}
92
93 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.
94
95 *Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
96 {code}
97 wo.external.root=/Users/mike/Developer/special/directory/Roots
98 {code}
99
Kieran Kelleher 172.1 100 *Tip:* A custom WebServer install directory can be specified to Wonder by adding the property 'wo.server.root' to the custom wilips properties file also.
Kieran Kelleher 170.1 101
102 {{/info}}