Skip to Content
Version 146.1 by Kieran Kelleher on 2010/09/27 01:34
Show last authors
1 == Introduction ==
2
3 Instead of downloading the Wonder binaries, working from the latest source code directly can have some advantages such as:
4
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
9 * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
10 * Discover the many Hidden Treasures of Wonder
11
12 == Source Frameworks Initial Installation ==
13
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:
15
16 {{code title="Procedure for WebObjects 5.4.X"}}
17
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
21
22 # Navigate into the working copy root
23 cd WonderSource
24
25 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
26 ant -Dwonder.patch=54 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 -Dwonder.patch=54 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
40 # Navigate into the working copy root
41 cd WonderSource
42
43 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
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
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
71 # Clean the previous build artifacts
72 ant -Dwonder.patch=54 clean
73
74 # Build from the latest source
75 ant -Dwonder.patch=54 frameworks
76
77 # Install the latest built frameworks
78 sudo ant -Dwonder.patch=54 frameworks.install
79
80 {{/code}}
81
82 {{code title="Procedure for WebObjects 5.3.X"}}
83
84 # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
85 cd ~/Roots/
86
87 # Delete all installed frameworks whose names match the built frameworks in this Roots build folder
88 for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
89
90 # Navigate to the original Wonder source directory that you created above during initial source installation
91 cd /path/to/WonderSource
92
93 # Update the source to the HEAD revision (aka latest). You can also use a specific svn
94 # repository version instead of the term 'HEAD', for example 11272
95 svn update --force --accept theirs-full --revision HEAD
96
97 # Clean, build and install the frameworks
98 ant clean; ant frameworks; sudo ant frameworks.install
99
100
101 {{/code}}
102
103 {{info}}
104
105 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.
106
107 {{/info}}
108
109 {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}}
110
111 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.
112
113 For example:
114
115 {code}
116 $ cd my/special/workspace/working/copy/of/Wonder
117 $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
118 {code}
119
120 {{/info}}