Skip to Content
Version 190.1 by Kieran Kelleher on 2010/09/13 14:58
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 * Ability to conveniently browse and search the source code and learn from the wisdom and experience of the WO committers
6 * Put breakpoints in and step through Wonder source when debugging your projects
7 * Provide opportunities to submit patches to bugs you might find in Wonder
8 * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
9 * Work with specific versions of Wonder in a project - good practice for quality control, especially for teams
10
11 == Downloading Wonder Source from Subversion ==
12
13 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:
14
15 {{code title="Procedure for WebObjects 5.4.X"}}
16
17 # Checkout the source from subversion repository into a new directory named "WonderSource"
18 svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision <ARG> WonderSource
19
20 # Navigate into the working copy root
21 cd WonderSource
22
23 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
24 ant -Dwonder.patch=54 frameworks
25
26 # Install the frameworks (this just copies the built frameworks from ~/Roots to the runtime Frameworks directory, usually at /Library/Framrworks
27 sudo ant -Dwonder.patch=54 frameworks.install
28
29 {{/code}}
30
31 * Open a terminal shell and navigate to the directory where you want to maintain the WonderSource directory and decide on a name of the folder that will contain the Wonder source. For this example, we will use the name //WonderSource//
32 * Perform initial checkout of Wonder source tree from Subversion head using the following command. This checks out the source into the directory //WonderSource//, automatically creating //WonderSource// if it does not exist.
33
34 {{noformat}}
35
36 svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder WonderSource
37
38 {{/noformat}}
39
40 * As often as you prefer you can keep this up to date as follows:
41
42 {{noformat}}
43
44 cd /path/to/WonderSource
45 svn up
46
47 {{/noformat}}
48
49 == Build and Install Wonder ==
50
51 * Follow the "Building with Ant" instructions in the BUILD.txt document in the Wonder directory
52
53 {{warning title="WebObjects 5.4.X Compatability"}}
54
55 The default instructions in Wonder's BUILD.txt produce binaries that are compatable with WO 5.3.3. If you are using WO 5.4.X, then you need to add the "-Dwonder.patch=54" option to the ant commands. For example:
56
57 ant \-Dwonder.patch=54 frameworks; sudo ant \-Dwonder.patch=54 frameworks.install
58
59 Alternatively, to avoid having to type the \-Dwonder.patch=54 option every time, one can put the line "wonder.patch=54" either in the wolips.properties file that resides in the \~/Library/Application Support/WOLips directory or in a build.properties file in the Wonder source root directory.
60
61 {{/warning}}
62
63 == Concepts ==
64
65 This complete procedure results in you having
66
67 * a Wonder directory with the whole Wonder source tree (directories, projects, frameworks, example apps, miscellaneous, etc.) inside.
68 * The binary Wonder frameworks ("ant frameworks") will be installed in /Library/Frameworks.
69 * If you ran "ant applications", they will be installed in ...
70 * If you ran "ant examples", they will be installed in ...