Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 139.1
edited by Lachlan Deck
on 2009/02/08 04:08
Change comment: Adjusting instructions for checking out Wonder trunk source to not check out branches.
To version 166.1
edited by Kieran Kelleher
on 2010/08/14 19:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ldeck
1 +XWiki.kieran
Content
... ... @@ -2,46 +2,47 @@
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 browse the source code and learn from the wisdom and experience of the WO committers
5 +* Ability to conveniently browse and search the source code and learn from the wisdom and experience of the WO committers
6 6  * Put breakpoints in and step through Wonder source when debugging your projects
7 7  * Provide opportunities to submit patches to bugs you might find in Wonder
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
9 9  
10 10  == Downloading Wonder Source from Subversion ==
11 11  
12 -* Decide on a directory where you will maintain the latest Wonder source tree on your hard drive. I have a directory ',,/WonderLatest' in my home folder.,,
13 -* Open a terminal shell and navigate to the directory
13 +* 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//
14 +* 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.
14 14  
15 15  {{noformat}}
16 16  
17 -mkdir ~/WonderLatest
18 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder WonderSource
18 18  
19 19  {{/noformat}}
20 20  
21 -* Next perform initial checkout of Wonder source tree from Subversion head using the following command. This creates a folder named Wonder
22 +* As often as you prefer you can keep this up to date as follows:
22 22  
23 23  {{noformat}}
24 24  
25 -svn co https://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder ~/WonderLatest
26 +cd /path/to/WonderSource
27 +svn up
26 26  
27 27  {{/noformat}}
28 28  
29 -* As often as you prefer you can keep this up to date as follows:
31 +== Build and Install Wonder ==
30 30  
31 -{{noformat}}
33 +* Follow the "Building with Ant" instructions in the BUILD.txt document in the Wonder directory
32 32  
33 -$ cd ~/WonderLatest
34 -$ svn up
35 +{{warning title="WebObjects 5.4.X Compatability"}}
35 35  
36 -{{/noformat}}
37 +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:
37 37  
38 -== Build and Install Wonder ==
39 +ant \-Dwonder.patch=54 frameworks; sudo ant \-Dwonder.patch=54 frameworks.install
39 39  
40 -* Follow the "Building with Ant" instructions in the BUILD.txt document in the Wonder directory
41 +{{/warning}}
41 41  
42 42  == Concepts ==
43 43  
44 -This complete procedure results in you having
45 +This complete procedure results in you having
45 45  
46 46  * a Wonder directory with the whole Wonder source tree (directories, projects, frameworks, example apps, miscellaneous, etc.) inside.
47 47  * The binary Wonder frameworks ("ant frameworks") will be installed in /Library/Frameworks.