Skip to Content
Version 154.1 by Kieran Kelleher on 2010/09/27 17:51
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 142.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 142.1 10 * Discover the many Hidden Treasures of Wonder
David Avendasora 112.1 11
Kieran Kelleher 142.1 12 == Source Frameworks Initial Installation ==
David Avendasora 112.1 13
Kieran Kelleher 144.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 the build and installation commands are slighly different for WebObjects 5.4.X. So procedures for both WebObjects 5.4.X and 5.3.X are shown below. Pick you poison:
miguel77mex 77.1 15
Kieran Kelleher 142.1 16 {{code title="Procedure for WebObjects 5.4.X"}}
miguel77mex 77.1 17
Kieran Kelleher 142.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 142.1 22 # Navigate into the working copy root
23 cd WonderSource
miguel77mex 77.1 24
Kieran Kelleher 142.1 25 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
Kieran Kelleher 154.1 26 ant frameworks
David Avendasora 128.1 27
Kieran Kelleher 142.1 28 # Install the frameworks (this just copies the built frameworks from ~/Roots to
29 # the runtime Frameworks directory, usually at /Library/Frameworks)
Kieran Kelleher 154.1 30 sudo ant frameworks.install
David Avendasora 128.1 31
Kieran Kelleher 142.1 32 {{/code}}
David Avendasora 128.1 33
Kieran Kelleher 142.1 34 {{code title="Procedure for WebObjects 5.3.X"}}
David Avendasora 128.1 35
Kieran Kelleher 142.1 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
David Avendasora 128.1 39
Kieran Kelleher 142.1 40 # Navigate into the working copy root
41 cd WonderSource
David Avendasora 118.1 42
Kieran Kelleher 142.1 43 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
44 ant frameworks
David Avendasora 124.1 45
Kieran Kelleher 142.1 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
David Avendasora 128.1 49
Kieran Kelleher 142.1 50 {{/code}}
51
52 == Source Frameworks Upgrade Installation ==
53
54 Assuming you already installed Wonder from source using the method outlined above, you can use the following procedure to upgrade to a newer, or just different version. Note that the procedure for both WebObjects 5.4.X and 5.3.X are outlined below. They are the same except for the last 3 ant commands.
55
56 {{code title="Procedure for WebObjects 5.4.X"}}
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
65 cd /path/to/WonderSource
66
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
70
Kieran Kelleher 154.1 71 # Clean, build and install the frameworks
72 ant clean; ant frameworks; sudo ant frameworks.install
Kieran Kelleher 142.1 73
74 {{/code}}
75
76 {{code title="Procedure for WebObjects 5.3.X"}}
77
78 # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
79 cd ~/Roots/
80
81 # Delete all installed frameworks whose names match the built frameworks in this Roots build folder
82 for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
83
84 # Navigate to the original Wonder source directory that you created above during initial source installation
85 cd /path/to/WonderSource
86
87 # Update the source to the HEAD revision (aka latest). You can also use a specific svn
88 # repository version instead of the term 'HEAD', for example 11272
89 svn update --force --accept theirs-full --revision HEAD
90
91 # Clean, build and install the frameworks
92 ant clean; ant frameworks; sudo ant frameworks.install
93
94
95 {{/code}}
96
97 {{info}}
98
99 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.
100
101 {{/info}}
102
103 {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}}
104
105 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.
106
107 For example:
108
109 {code}
Kieran Kelleher 148.1 110 $ cd my/special/purpose/working/copy/of/Wonder
Kieran Kelleher 142.1 111 $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
112 {code}
113
Kieran Kelleher 148.1 114 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.
Kieran Kelleher 152.1 115
Kieran Kelleher 148.1 116 *Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
117 {code}
118 wo.external.root=/Users/mike/Developer/special/directory/Roots
119 {code}
120
Kieran Kelleher 152.1 121 *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.
122
Kieran Kelleher 142.1 123 {{/info}}