Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 165.1
edited by Kieran Kelleher
on 2010/09/17 12:56
on 2010/09/17 12:56
Change comment:
There is no comment for this version
To version 170.1
edited by Kieran Kelleher
on 2011/03/25 19:17
on 2011/03/25 19:17
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Download Wonder Source, Build andInstall1 +Download Wonder Source, Build, Install and Upgrade - Content
-
... ... @@ -11,36 +11,24 @@ 11 11 12 12 == Source Frameworks Initial Installation == 13 13 14 - Opena terminal and navigate to adirectorywhereyouwanttomaintaina source"workingcopy"and justusethefollowingeasy-peasycommandstodownloadthe Wondersource.Note that thebuildand installationcommandsareslighlydifferent for WebObjects5.4.X. So proceduresfor both WebObjects5.4.X and5.3.X are shown below.Pick you poison: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 15 16 - {{code title="Procedure forWebObjects5.4.X"}}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 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/trunk/Wonder --revision HEAD WonderSource 18 +{{code title="Cloning Project Wonder for the First Time"}} 21 21 22 -# Navigate into the working copy root 23 -cd WonderSource 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 24 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 40 # Navigate into the working copy root 41 41 cd WonderSource 42 42 43 -# Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir) 27 +# If you are still using old WebObjects 5.3.3, then you need to execute one git command at this point 28 +# before you build Wonder to switch to the branch that is source-compatible with WO 5.3.3. See the tip at the bottom of the page. 29 + 30 +# Build the frameworks from the source (Assumes you are using WebObjects 5.4.3, 31 +# which is currently compatible with 'master' branch. See note below for WebObjects 5.3.3 compatible install) 44 44 ant frameworks 45 45 46 46 # Install the frameworks (this just copies the built frameworks from ~/Roots to ... ... @@ -51,9 +51,9 @@ 51 51 52 52 == Source Frameworks Upgrade Installation == 53 53 54 -Assuming you already installed Wonder from source using the method outlined above, you can use the following procedure t oupgradeoawer, or justdifferentversion.Note that the procedurefor both WebObjects 5.4.Xand 5.3.X are outlinedbelow. They arethe same except for the last3 ant commands.42 +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. 55 55 56 -{{code title=" ProcedureforWebObjects 5.4.X"}}44 +{{code title="Updating your Source"}} 57 57 58 58 # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above 59 59 cd ~/Roots/ ... ... @@ -64,44 +64,49 @@ 64 64 # Navigate to the original Wonder source directory that you created above during initial source installation 65 65 cd /path/to/WonderSource 66 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 55 +# Pull the changes you do not have and merge them with your local repository 56 +git pull 70 70 71 -# Clean the previousbuild artifacts72 -ant -Dwonder.patch=54clean58 +# Clean, build and install the frameworks 59 +ant clean; ant frameworks; sudo ant frameworks.install 73 73 74 -# Build from the latest source 75 -ant -Dwonder.patch=54 frameworks 61 +{{/code}} 76 76 77 -# Install the latest built frameworks 78 -sudo ant -Dwonder.patch=54 frameworks.install 63 +{{info value="Legacy WebObjects 5.3.3 Compatability"}} 79 79 80 -{{/code}} 65 +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: 66 + 67 +{code} 68 +git checkout --track origin/Wonder_5_0_0_Legacy 69 +{code} 70 + 81 81 82 -{{ code title="Procedurefor WebObjects 5.3.X"}}72 +{{/info}} 83 83 84 -# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above 85 -cd ~/Roots/ 74 +{{info}} 86 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 76 +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. 89 89 90 -# Navigate to the original Wonder source directory that you created above during initial source installation 91 -cd /path/to/WonderSource 78 +{{/info}} 92 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 80 +{{info value="Custom Development Enviroment File layout using Custom wolips.properties"}} 96 96 97 -# Clean, build and install the frameworks 98 -ant clean; ant frameworks; sudo ant frameworks.install 82 +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. 99 99 84 +For example: 100 100 101 -{{/code}} 86 +{code} 87 +$ cd my/special/purpose/clone/of/Wonder 88 +$ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties 89 +{code} 102 102 103 - {{info}}91 +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. 104 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. 93 +*Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example 94 +{code} 95 +wo.external.root=/Users/mike/Developer/special/directory/Roots 96 +{code} 106 106 98 +*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. 99 + 107 107 {{/info}}