Skip to Content
Version 183.1 by Kieran Kelleher on 2011/03/25 19:12
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 174.1 14 As of March 25th, 2011, Wonder is maintained on github. So git is what we use to get a local clone of the repository allowing us to directly use Wonder source.
miguel77mex 77.1 15
Kieran Kelleher 174.1 16 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 own hard-drive.
miguel77mex 77.1 17
Kieran Kelleher 174.1 18 {{code title="Cloning Project Wonder for the First Time"}}
David Avendasora 128.1 19
Kieran Kelleher 174.1 20 # Clone the source repository from github into a new directory named "WonderSource".
21 # Note the URL shown here is the public read-only URL. Committers should use the SSH form of the URL for read-write
22 git clone git://github.com/projectwonder/wonder.git WonderSource
miguel77mex 77.1 23
Kieran Kelleher 170.1 24 # Navigate into the working copy root
25 cd WonderSource
David Avendasora 128.1 26
Kieran Kelleher 176.1 27 # Build the frameworks from the source (Assumes you are using WebObjects 5.4.3,
28 # which is currently compatible with 'master' branch. See note below for WebObjects 5.3.3 compatible install)
Kieran Kelleher 170.1 29 ant frameworks
30
31 # Install the frameworks (this just copies the built frameworks from ~/Roots to
32 # the runtime Frameworks directory, usually at /Library/Frameworks)
33 sudo ant frameworks.install
34
35 {{/code}}
36
37 == Source Frameworks Upgrade Installation ==
38
Kieran Kelleher 174.1 39 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.
Kieran Kelleher 170.1 40
Kieran Kelleher 176.1 41 {{code title="Updating your Source"}}
Kieran Kelleher 170.1 42
43 # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
44 cd ~/Roots/
45
46 # Delete all installed frameworks whose names match the built frameworks in this Roots build folder
47 for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
48
49 # Navigate to the original Wonder source directory that you created above during initial source installation
Kieran Kelleher 142.1 50 cd /path/to/WonderSource
51
Kieran Kelleher 174.1 52 # Pull the changes you do not have and merge them with your local repository
53 git pull
Kieran Kelleher 142.1 54
Kieran Kelleher 170.1 55 # Clean, build and install the frameworks
56 ant clean; ant frameworks; sudo ant frameworks.install
Kieran Kelleher 142.1 57
Kieran Kelleher 170.1 58 {{/code}}
Kieran Kelleher 156.1 59
Kieran Kelleher 170.1 60 {{info}}
tmk 168.1 61
Kieran Kelleher 174.1 62 If 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.
Kieran Kelleher 142.1 63
Kieran Kelleher 170.1 64 {{/info}}
Kieran Kelleher 142.1 65
Kieran Kelleher 170.1 66 {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}}
Kieran Kelleher 142.1 67
Kieran Kelleher 174.1 68 If 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.
Kieran Kelleher 170.1 69
70 For example:
71
72 {code}
Kieran Kelleher 174.1 73 $ cd my/special/purpose/clone/of/Wonder
Kieran Kelleher 170.1 74 $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
75 {code}
76
77 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.
78
79 *Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
80 {code}
81 wo.external.root=/Users/mike/Developer/special/directory/Roots
82 {code}
83
Kieran Kelleher 174.1 84 *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.
Kieran Kelleher 170.1 85
86 {{/info}}
Kieran Kelleher 178.1 87
88 {{info value="Legacy WebObjects 5.3.3 Compatability"}}
89
90 If you are still stuck on WebObjects 5.3.3, for whatever reason, then you need to checkout and switch to the Wonder_5_0_0_Legacy branch *before* you build (before you run 'ant frameworks'). And this is *much* easier with git than it used to be with subversion. Just one command:
91 {code}
92 git checkout --track origin/Wonder_5_0_0_Legacy
Kieran Kelleher 180.1 93 {code}
Kieran Kelleher 178.1 94
95 {{/info}}