Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 189.1
edited by Kieran Kelleher
on 2010/09/13 15:10
on 2010/09/13 15:10
Change comment:
There is no comment for this version
To version 162.1
edited by Kieran Kelleher
on 2010/09/27 01:33
on 2010/09/27 01:33
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,13 +2,14 @@ 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 -* 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 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 8 8 * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs 9 -* Work withspecificversionsofWonderina project - good practice for quality control,especiallyforteams10 +* Discover the many Hidden Treasures of Wonder 10 10 11 -== Source Frameworks Initial Installation Procedure==12 +== Source Frameworks Initial Installation == 12 12 13 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 14 ... ... @@ -15,7 +15,8 @@ 15 15 {{code title="Procedure for WebObjects 5.4.X"}} 16 16 17 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 +# 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 20 # Navigate into the working copy root 21 21 cd WonderSource ... ... @@ -23,8 +23,8 @@ 23 23 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir) 24 24 ant -Dwonder.patch=54 frameworks 25 25 26 -# Install the frameworks (this just copies the built frameworks from ~/Roots to 27 -# the runtime Frameworks directory, usually at /Library/Fram rworks28 +# Install the frameworks (this just copies the built frameworks from ~/Roots to 29 +# the runtime Frameworks directory, usually at /Library/Frameworks) 28 28 sudo ant -Dwonder.patch=54 frameworks.install 29 29 30 30 {{/code}} ... ... @@ -32,7 +32,8 @@ 32 32 {{code title="Procedure for WebObjects 5.3.X"}} 33 33 34 34 # Checkout the source from subversion repository into a new directory named "WonderSource" 35 -svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision <ARG> 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 36 36 37 37 # Navigate into the working copy root 38 38 cd WonderSource ... ... @@ -40,8 +40,8 @@ 40 40 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir) 41 41 ant frameworks 42 42 43 -# Install the frameworks (this just copies the built frameworks from ~/Roots to 44 -# the runtime Frameworks directory, usually at /Library/Fram rworks46 +# Install the frameworks (this just copies the built frameworks from ~/Roots to 47 +# the runtime Frameworks directory, usually at /Library/Frameworks) 45 45 sudo ant frameworks.install 46 46 47 47 {{/code}} ... ... @@ -56,12 +56,12 @@ 56 56 cd ~/Roots/ 57 57 58 58 # Delete all installed frameworks whose names match the built frameworks in this Roots build folder 59 - $for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done62 +for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done 60 60 61 61 # Navigate to the original Wonder source directory that you created above during initial source installation 62 - $cd /path/to/WonderSource65 +cd /path/to/WonderSource 63 63 64 -# Update the source to the HEAD revision (aka latest). You can also use a specific svn 67 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn 65 65 # repository version instead of the term 'HEAD', for example 11272 66 66 svn update --force --accept theirs-full --revision HEAD 67 67 ... ... @@ -82,28 +82,36 @@ 82 82 cd ~/Roots/ 83 83 84 84 # Delete all installed frameworks whose names match the built frameworks in this Roots build folder 85 - $for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done88 +for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done 86 86 87 87 # Navigate to the original Wonder source directory that you created above during initial source installation 88 - $cd /path/to/WonderSource91 +cd /path/to/WonderSource 89 89 90 -# Update the source to the HEAD revision (aka latest). You can also use a specific svn 93 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn 91 91 # repository version instead of the term 'HEAD', for example 11272 92 92 svn update --force --accept theirs-full --revision HEAD 93 93 94 -# Clean the previousbuild artifacts95 -ant clean 97 +# Clean, build and install the frameworks 98 +ant clean; ant frameworks; sudo ant frameworks.install 96 96 97 -# Build from the latest source 98 -ant frameworks 99 99 100 -# Install the latest built frameworks 101 -sudo frameworks.install 102 - 103 103 {{/code}} 104 104 105 105 {{info}} 106 106 107 -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. 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. 108 108 109 109 {{/info}} 108 + 109 +{{info value="Custom Development Enviroment File layout using Custom wolips.properties"}} 110 + 111 +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 and build script will supersede all other settings with the settings in that file. 112 + 113 +For example: 114 + 115 +{code} 116 +$ cd my/special/workspace/working/copy/of/Wonder 117 +$ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties 118 +{code} 119 + 120 +{{/info}}