Last modified by Bastian Triller on 2013/10/05 10:40

From version 191.1
edited by Kieran Kelleher
on 2010/09/13 14:58
Change comment: There is no comment for this version
To version 173.1
edited by Kieran Kelleher
on 2010/10/04 21:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Download Wonder Source, Build and Install
1 +Download Wonder Source, Build, Install and Upgrade
Content
... ... @@ -2,69 +2,101 @@
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 with specific versions of Wonder in a project - good practice for quality control, especially for teams
10 +* Discover the many Hidden Treasures of Wonder
10 10  
11 -== Downloading Wonder Source from Subversion ==
12 +== Source Frameworks Initial Installation ==
12 12  
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 +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.
14 14  
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
22 22  
23 23  # Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
24 -ant -Dwonder.patch=54 frameworks
26 +ant frameworks
25 25  
26 -# Install the frameworks (this just copies the built frameworks from ~/Roots to the runtime Frameworks directory, usually at /Library/Framrworks
27 -sudo ant -Dwonder.patch=54 frameworks.install
28 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
29 +# the runtime Frameworks directory, usually at /Library/Frameworks)
30 +sudo ant frameworks.install
28 28  
29 29  {{/code}}
30 30  
31 -* Open a terminal shell and navigate to the directory where you want to maintain the WonderSource directory and decide on a name of the folder that will contain the Wonder source. For this example, we will use the name //WonderSource//
32 -* Perform initial checkout of Wonder source tree from Subversion head using the following command. This checks out the source into the directory //WonderSource//, automatically creating //WonderSource// if it does not exist.
34 +{{code title="Procedure for WebObjects 5.3.X"}}
33 33  
34 -{{noformat}}
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
35 35  
36 -svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder WonderSource
40 +# Navigate into the working copy root
41 +cd WonderSource
37 37  
38 -{{/noformat}}
43 +# Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
44 +ant frameworks
39 39  
40 -* As often as you prefer you can keep this up to date as follows:
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
41 41  
42 -{{noformat}}
50 +{{/code}}
43 43  
52 +== Source Frameworks Upgrade Installation ==
53 +
54 +Assuming you already installed Wonder from source using the method outlined above, and you are using the branch of Wonder appropriate to your WebObjects version, you can use the following procedure to upgrade to a newer, or just different version, as long as that version is greater than repository version 11387 (Sep 27, 2010, which was when the WO 5.4 branch was first introduced).
55 +
56 +{{code title="Procedure for WebObjects 5.3.X or 5.4.X"}}
57 +
58 +# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
59 +cd ~/Roots/
60 +
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
63 +
64 +# Navigate to the original Wonder source directory that you created above during initial source installation
44 44  cd /path/to/WonderSource
45 -svn up
46 46  
47 -{{/noformat}}
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
48 48  
49 -== Build and Install Wonder ==
71 +# Clean, build and install the frameworks
72 +ant clean; ant frameworks; sudo ant frameworks.install
50 50  
51 -* Follow the "Building with Ant" instructions in the BUILD.txt document in the Wonder directory
74 +{{/code}}
52 52  
53 -{{warning title="WebObjects 5.4.X Compatability"}}
76 +{{info}}
54 54  
55 -The default instructions in Wonder's BUILD.txt produce binaries that are compatable with WO 5.3.3. If you are using WO 5.4.X, then you need to add the "-Dwonder.patch=54" option to the ant commands. For example:
78 +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.
56 56  
57 -ant \-Dwonder.patch=54 frameworks; sudo ant \-Dwonder.patch=54 frameworks.install
80 +{{/info}}
58 58  
59 -Alternatively, to avoid having to type the \-Dwonder.patch=54 option every time, one can put the line "wonder.patch=54" either in the wolips.properties file that resides in the \~/Library/Application Support/WOLips directory or in a build.properties file in the Wonder source root directory.
82 +{{info value="Custom Development Enviroment File layout using Custom wolips.properties"}}
60 60  
61 -{{/warning}}
84 +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.
62 62  
63 -== Concepts ==
86 +For example:
64 64  
65 -This complete procedure results in you having
88 +{code}
89 +$ cd my/special/purpose/working/copy/of/Wonder
90 +$ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
91 +{code}
66 66  
67 -* a Wonder directory with the whole Wonder source tree (directories, projects, frameworks, example apps, miscellaneous, etc.) inside.
68 -* The binary Wonder frameworks ("ant frameworks") will be installed in /Library/Frameworks.
69 -* If you ran "ant applications", they will be installed in ...
70 -* If you ran "ant examples", they will be installed in ...
93 +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.
94 +
95 +*Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
96 +{code}
97 +wo.external.root=/Users/mike/Developer/special/directory/Roots
98 +{code}
99 +
100 +*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 +
102 +{{/info}}