Wiki source code of Download Wonder Source, Build, Install and Upgrade
Version 175.1 by Kieran Kelleher on 2011/03/25 18:47
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | 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. | ||
| 15 | |||
| 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. | ||
| 17 | |||
| 18 | {{code title="Cloning Project Wonder for the First Time"}} | ||
| 19 | |||
| 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 | ||
| 23 | |||
| 24 | # Navigate into the working copy root | ||
| 25 | cd WonderSource | ||
| 26 | |||
| 27 | # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir) | ||
| 28 | ant frameworks | ||
| 29 | |||
| 30 | # Install the frameworks (this just copies the built frameworks from ~/Roots to | ||
| 31 | # the runtime Frameworks directory, usually at /Library/Frameworks) | ||
| 32 | sudo ant frameworks.install | ||
| 33 | |||
| 34 | {{/code}} | ||
| 35 | |||
| 36 | == Source Frameworks Upgrade Installation == | ||
| 37 | |||
| 38 | 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. | ||
| 39 | |||
| 40 | {{code title="Procedure for WebObjects 5.3.X or 5.4.X"}} | ||
| 41 | |||
| 42 | # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above | ||
| 43 | cd ~/Roots/ | ||
| 44 | |||
| 45 | # Delete all installed frameworks whose names match the built frameworks in this Roots build folder | ||
| 46 | for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done | ||
| 47 | |||
| 48 | # Navigate to the original Wonder source directory that you created above during initial source installation | ||
| 49 | cd /path/to/WonderSource | ||
| 50 | |||
| 51 | # Pull the changes you do not have and merge them with your local repository | ||
| 52 | git pull | ||
| 53 | |||
| 54 | # Clean, build and install the frameworks | ||
| 55 | ant clean; ant frameworks; sudo ant frameworks.install | ||
| 56 | |||
| 57 | {{/code}} | ||
| 58 | |||
| 59 | {{info}} | ||
| 60 | |||
| 61 | 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. | ||
| 62 | |||
| 63 | {{/info}} | ||
| 64 | |||
| 65 | {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}} | ||
| 66 | |||
| 67 | 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. | ||
| 68 | |||
| 69 | For example: | ||
| 70 | |||
| 71 | {code} | ||
| 72 | $ cd my/special/purpose/clone/of/Wonder | ||
| 73 | $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties | ||
| 74 | {code} | ||
| 75 | |||
| 76 | 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. | ||
| 77 | |||
| 78 | *Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example | ||
| 79 | {code} | ||
| 80 | wo.external.root=/Users/mike/Developer/special/directory/Roots | ||
| 81 | {code} | ||
| 82 | |||
| 83 | *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. | ||
| 84 | |||
| 85 | {{/info}} |