Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 126.1
edited by Paul Hoadley
on 2011/03/27 03:10
on 2011/03/27 03:10
Change comment:
Added a couple of hyperlinks.
To version 142.1
edited by Kieran Kelleher
on 2010/09/27 17:58
on 2010/09/27 17:58
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. paulh1 +XWiki.kieran - Content
-
... ... @@ -2,33 +2,27 @@ 2 2 3 3 Instead of downloading the Wonder binaries, working from the latest source code directly can have some advantages such as: 4 4 5 -* Learn alotabout WebObjects and EOF (andJava developmentstyles)5 +* Learn very much about WebObjects and EOF (and java dev styles?) 6 6 * Easily browse and search the source 7 -* Work with a specific s ource controlversion (teams, quality control, development cycles)7 +* Work with a specific svn version (teams, quality control, development cycles) 8 8 * Provide opportunities to submit patches for bug fixes or enhancements 9 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 .10 +* Discover the many Hidden Treasures of Wonder 11 11 12 12 == Source Frameworks Initial Installation == 13 13 14 - AsofMarch 25th,2011, Wonderismaintainedon[[GitHub>>https://github.com/]].So[[Git>>http://git-scm.com/]]iswhat weusetoget a localclone of the repositoryallowingus todirectlyuseWondersource.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 as of repository version 11387 (Sep 27, 2010) the Wonder repository URL is the only difference between the Wonder source procedure for WebObjects 5.3.3 and WebObjects 5.4.3 installation. For your copy/paste convenience, the full procedures for both WebObjects 5.4.X and 5.3.X are shown below. WebObjects 5.4.3 and the Wonder branch for same is recommended and is where the most features are expected to be found. 15 15 16 - Open a terminal and navigate toadirectorywhere you wantto maintain a sourceworking copy" andjust usethefollowingeasy-peasycommandsto clone Wondersourceto your own hard-drive.16 +{{code title="Procedure for WebObjects 5.4.X"}} 17 17 18 -{{code title="Cloning Project Wonder for the First Time"}} 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 19 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 24 # Navigate into the working copy root 25 25 cd WonderSource 26 26 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) 25 +# Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir) 32 32 ant frameworks 33 33 34 34 # Install the frameworks (this just copies the built frameworks from ~/Roots to ... ... @@ -37,22 +37,29 @@ 37 37 38 38 {{/code}} 39 39 40 -{{ infovalue="LegacyWebObjects 5.3.3 Compatability"}}34 +{{code title="Procedure for WebObjects 5.3.X"}} 41 41 42 -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: 43 - 44 -{code} 45 -git checkout --track origin/Wonder_5_0_0_Legacy 46 -{code} 47 - 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 48 48 49 -{{/info}} 40 +# Navigate into the working copy root 41 +cd WonderSource 50 50 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 + 51 51 == Source Frameworks Upgrade Installation == 52 52 53 -Assuming you already cloned andinstalled Wonder from source using the method outlined above, you can use the following procedurepullthelatestchanges intoyourlocal repository.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. 54 54 55 -{{code title=" Updating yourSource"}}56 +{{code title="Procedure for WebObjects 5.4.X"}} 56 56 57 57 # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above 58 58 cd ~/Roots/ ... ... @@ -63,8 +63,9 @@ 63 63 # Navigate to the original Wonder source directory that you created above during initial source installation 64 64 cd /path/to/WonderSource 65 65 66 -# Pull the changes you do not have and merge them with your local repository 67 -git pull 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 68 68 69 69 # Clean, build and install the frameworks 70 70 ant clean; ant frameworks; sudo ant frameworks.install ... ... @@ -71,22 +71,41 @@ 71 71 72 72 {{/code}} 73 73 74 - 76 +{{code title="Procedure for WebObjects 5.3.X"}} 75 75 78 +# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above 79 +cd ~/Roots/ 80 + 81 +# Delete all installed frameworks whose names match the built frameworks in this Roots build folder 82 +for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done 83 + 84 +# Navigate to the original Wonder source directory that you created above during initial source installation 85 +cd /path/to/WonderSource 86 + 87 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn 88 +# repository version instead of the term 'HEAD', for example 11272 89 +svn update --force --accept theirs-full --revision HEAD 90 + 91 +# Clean, build and install the frameworks 92 +ant clean; ant frameworks; sudo ant frameworks.install 93 + 94 + 95 +{{/code}} 96 + 76 76 {{info}} 77 77 78 -If you have any trouble or errors due to your localrepository getting hosed, then simply delete the entirelocalrepository directory, the \~/Roots directory and just start over using the initial sourceclone andinstallation procedure outlined above.99 +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. 79 79 80 80 {{/info}} 81 81 82 82 {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}} 83 83 84 -If you have a custom wolips properties file for a specific workspace and you want to have a specific Wonder c lonefor 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.105 +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. 85 85 86 86 For example: 87 87 88 88 {code} 89 -$ cd my/special/purpose/ clone/of/Wonder110 +$ cd my/special/purpose/working/copy/of/Wonder 90 90 $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties 91 91 {code} 92 92 ... ... @@ -97,6 +97,6 @@ 97 97 wo.external.root=/Users/mike/Developer/special/directory/Roots 98 98 {code} 99 99 100 -*Tip:* A custom WebServer install directory can be specified to Wonder by adding the property 'wo.server.root' to the custom w olips properties file also.121 +*Tip:* A custom WebServer install directory can be specified to Wonder by adding the property 'wo.server.root' to the custom wilips properties file also. 101 101 102 102 {{/info}}