Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 155.1
edited by Kieran Kelleher
on 2010/09/27 17:51
on 2010/09/27 17:51
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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Download Wonder Source, Build ,Installand Upgrade1 +Download Wonder Source, Build and Install - Content
-
... ... @@ -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 frameworks 26 +ant -Dwonder.patch=54 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 frameworks.install 30 +sudo ant -Dwonder.patch=54 frameworks.install 31 31 32 32 {{/code}} 33 33 ... ... @@ -68,9 +68,15 @@ 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 ,build and install theframeworks72 -ant clean; ant frameworks; sudo ant frameworks.install71 +# Clean the previous build artifacts 72 +ant -Dwonder.patch=54 clean 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 + 74 74 {{/code}} 75 75 76 76 {{code title="Procedure for WebObjects 5.3.X"}} ... ... @@ -102,22 +102,13 @@ 102 102 103 103 {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}} 104 104 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 layoutpoperties with theproperties in that file.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. 106 106 107 107 For example: 108 108 109 109 {code} 110 -$ cd my/special/ purpose/working/copy/of/Wonder116 +$ cd my/special/workspace/working/copy/of/Wonder 111 111 $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties 112 112 {code} 113 113 114 -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. 115 - 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 - 123 123 {{/info}}