Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 144.1
edited by Kieran Kelleher
on 2010/09/27 04:02
on 2010/09/27 04:02
Change comment:
There is no comment for this version
To version 143.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
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Download Wonder Source, Build andInstall1 +Download Wonder Source, Build, Install and Upgrade - Content
-
... ... @@ -11,7 +11,7 @@ 11 11 12 12 == Source Frameworks Initial Installation == 13 13 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 buildandinstallationcommandsarelighly different for WebObjects 5.4.X.So procedures for both WebObjects 5.4.X and 5.3.X are shown below.Pickyou poison: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 16 {{code title="Procedure for WebObjects 5.4.X"}} 17 17 ... ... @@ -23,11 +23,11 @@ 23 23 cd WonderSource 24 24 25 25 # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir) 26 -ant -Dwonder.patch=54frameworks26 +ant frameworks 27 27 28 28 # Install the frameworks (this just copies the built frameworks from ~/Roots to 29 29 # the runtime Frameworks directory, usually at /Library/Frameworks) 30 -sudo ant -Dwonder.patch=54frameworks.install30 +sudo ant frameworks.install 31 31 32 32 {{/code}} 33 33 ... ... @@ -68,15 +68,9 @@ 68 68 # repository version instead of the term 'HEAD', for example 11272 69 69 svn update --force --accept theirs-full --revision HEAD 70 70 71 -# Clean the previousbuild artifacts72 -ant -Dwonder.patch=54clean71 +# Clean, build and install the frameworks 72 +ant clean; ant frameworks; sudo ant frameworks.install 73 73 74 -# Build from the latest source 75 -ant -Dwonder.patch=54 frameworks 76 - 77 -# Install the latest built frameworks 78 -sudo ant -Dwonder.patch=54 frameworks.install 79 - 80 80 {{/code}} 81 81 82 82 {{code title="Procedure for WebObjects 5.3.X"}} ... ... @@ -119,4 +119,11 @@ 119 119 120 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 121 116 +*Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example 117 +{code} 118 +wo.external.root=/Users/mike/Developer/special/directory/Roots 119 +{code} 120 + 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. 122 + 122 122 {{/info}}