Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 151.1
edited by Kieran Kelleher
on 2010/09/27 04:05
Change comment: There is no comment for this version
To version 186.1
edited by Kieran Kelleher
on 2010/09/13 15:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,7 @@
9 9  * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
10 10  * Discover the many Hidden Treasures of Wonder
11 11  
12 -== Source Frameworks Initial Installation ==
12 +== Source Frameworks Initial Installation Procedure ==
13 13  
14 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 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:
15 15  
... ... @@ -16,8 +16,7 @@
16 16  {{code title="Procedure for WebObjects 5.4.X"}}
17 17  
18 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 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision <ARG> WonderSource
21 21  
22 22  # Navigate into the working copy root
23 23  cd WonderSource
... ... @@ -25,8 +25,8 @@
25 25  # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
26 26  ant -Dwonder.patch=54 frameworks
27 27  
28 -# Install the frameworks (this just copies the built frameworks from ~/Roots to
29 -# the runtime Frameworks directory, usually at /Library/Frameworks)
27 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
28 +# the runtime Frameworks directory, usually at /Library/Framrworks
30 30  sudo ant -Dwonder.patch=54 frameworks.install
31 31  
32 32  {{/code}}
... ... @@ -34,8 +34,7 @@
34 34  {{code title="Procedure for WebObjects 5.3.X"}}
35 35  
36 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
36 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision <ARG> WonderSource
39 39  
40 40  # Navigate into the working copy root
41 41  cd WonderSource
... ... @@ -43,8 +43,8 @@
43 43  # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
44 44  ant frameworks
45 45  
46 -# Install the frameworks (this just copies the built frameworks from ~/Roots to
47 -# the runtime Frameworks directory, usually at /Library/Frameworks)
44 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
45 +# the runtime Frameworks directory, usually at /Library/Framrworks
48 48  sudo ant frameworks.install
49 49  
50 50  {{/code}}
... ... @@ -59,12 +59,12 @@
59 59  cd ~/Roots/
60 60  
61 61  # Delete all installed frameworks whose names match the built frameworks in this Roots build folder
62 -for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
60 +$ for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
63 63  
64 64  # Navigate to the original Wonder source directory that you created above during initial source installation
65 -cd /path/to/WonderSource
63 +$ cd /path/to/WonderSource
66 66  
67 -# Update the source to the HEAD revision (aka latest). You can also use a specific svn
65 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn
68 68  # repository version instead of the term 'HEAD', for example 11272
69 69  svn update --force --accept theirs-full --revision HEAD
70 70  
... ... @@ -85,42 +85,28 @@
85 85  cd ~/Roots/
86 86  
87 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
86 +$ for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
89 89  
90 90  # Navigate to the original Wonder source directory that you created above during initial source installation
91 -cd /path/to/WonderSource
89 +$ cd /path/to/WonderSource
92 92  
93 -# Update the source to the HEAD revision (aka latest). You can also use a specific svn
91 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn
94 94  # repository version instead of the term 'HEAD', for example 11272
95 95  svn update --force --accept theirs-full --revision HEAD
96 96  
97 -# Clean, build and install the frameworks
98 -ant clean; ant frameworks; sudo ant frameworks.install
95 +# Clean the previous build artifacts
96 +ant clean
99 99  
98 +# Build from the latest source
99 +ant frameworks
100 100  
101 +# Install the latest built frameworks
102 +sudo frameworks.install
103 +
101 101  {{/code}}
102 102  
103 103  {{info}}
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.
108 +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.
106 106  
107 107  {{/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 build script will supersede all other filesystem layout poperties with the properties in that file.
112 -
113 -For example:
114 -
115 -{code}
116 -$ cd my/special/purpose/working/copy/of/Wonder
117 -$ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
118 -{code}
119 -
120 -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.
121 -*Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
122 -{code}
123 -wo.external.root=/Users/mike/Developer/special/directory/Roots
124 -{code}
125 -
126 -{{/info}}