Skip to Content
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
Change comment: There is no comment for this version
To version 209.1
edited by franc
on 2010/09/13 17:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kieran
1 +XWiki.franc
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 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 -== 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  
... ... @@ -21,11 +21,11 @@
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
25 +ant -DWonder.patch=54 frameworks
25 25  
26 -# Install the frameworks (this just copies the built frameworks from ~/Roots to
27 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
27 27  # the runtime Frameworks directory, usually at /Library/Framrworks
28 -sudo ant -Dwonder.patch=54 frameworks.install
29 +sudo ant -DWonder.patch=54 frameworks.install
29 29  
30 30  {{/code}}
31 31  
... ... @@ -40,7 +40,7 @@
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 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
44 44  # the runtime Frameworks directory, usually at /Library/Framrworks
45 45  sudo ant frameworks.install
46 46  
... ... @@ -61,7 +61,7 @@
61 61  # Navigate to the original Wonder source directory that you created above during initial source installation
62 62  $ cd /path/to/WonderSource
63 63  
64 -# 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
65 65  # repository version instead of the term 'HEAD', for example 11272
66 66  svn update --force --accept theirs-full --revision HEAD
67 67  
... ... @@ -87,7 +87,7 @@
87 87  # Navigate to the original Wonder source directory that you created above during initial source installation
88 88  $ cd /path/to/WonderSource
89 89  
90 -# 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
91 91  # repository version instead of the term 'HEAD', for example 11272
92 92  svn update --force --accept theirs-full --revision HEAD
93 93  
... ... @@ -104,6 +104,6 @@
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.
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.
108 108  
109 109  {{/info}}