Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 193.1
edited by tmk
on 2010/09/10 02:30
Change comment: There is no comment for this version
To version 210.1
edited by Kieran Kelleher
on 2010/01/11 12:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.tmk
1 +XWiki.kieran
Content
... ... @@ -2,28 +2,35 @@
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
5 +* Ability to browse 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
10 10  
11 11  == Downloading Wonder Source from Subversion ==
12 12  
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.
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
15 15  
16 16  {{noformat}}
17 17  
18 -svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder WonderSource
17 +mkdir ~/WonderLatest
19 19  
20 20  {{/noformat}}
21 21  
21 +* Next perform initial checkout of Wonder source tree from Subversion head using the following command. This creates a folder named Wonder
22 +
23 +{{noformat}}
24 +
25 +svn co https://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder ~/WonderLatest
26 +
27 +{{/noformat}}
28 +
22 22  * As often as you prefer you can keep this up to date as follows:
23 23  
24 24  {{noformat}}
25 25  
26 -cd /path/to/WonderSource
33 +cd ~/WonderLatest
27 27  svn up
28 28  
29 29  {{/noformat}}
... ... @@ -36,15 +36,13 @@
36 36  
37 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:
38 38  
39 -ant \-Dwonder.patch=54 frameworks; sudo ant \-Dwonder.patch=54 frameworks.install
46 +ant -Dwonder.patch=54 frameworks; sudo ant -Dwonder.patch=54 frameworks.install
40 40  
41 -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.
42 -
43 43  {{/warning}}
44 44  
45 45  == Concepts ==
46 46  
47 -This complete procedure results in you having
52 +This complete procedure results in you having
48 48  
49 49  * a Wonder directory with the whole Wonder source tree (directories, projects, frameworks, example apps, miscellaneous, etc.) inside.
50 50  * The binary Wonder frameworks ("ant frameworks") will be installed in /Library/Frameworks.