Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 114.1
edited by David Avendasora
on 2011/04/25 12:42
Change comment: There is no comment for this version
To version 105.1
edited by Kieran Kelleher
on 2007/06/27 10:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Downloading, Building, Installing and Upgrading Wonder Source Code
1 +Download Wonder Source, Build and Install
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.kieran
Content
... ... @@ -2,120 +2,32 @@
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 -* Learn a lot about WebObjects and EOF (and Java development styles)
6 -* Easily browse and search the source
7 -* Work with a specific source control version (teams, quality control, development cycles)
8 -* Provide opportunities to submit patches for bug fixes or enhancements
5 +* Ability to browse 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
9 9  * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
10 -* Discover the many Hidden Treasures of Wonder.
11 11  
12 -== Download Project Wonder Source Code ==
10 +This documents my 'ideal' setup on my own system. I am sure there are variations. Wiki contributors may want to add other pages for what they consider other ideal Wonder setups
13 13  
14 -{{tip title="Now with more Git"}}
15 -As of March 25th, 2011 the Wonder source code is now maintained on [GitHub|https://github.com/] at [https://github.com/projectwonder]. So you'll need to be familiar with the [Git|http://git-scm.com/] Source Code Management system. You will use it to checkout a local copy of the repository (a "clone" in Git terms) allowing you to have direct access to the Wonder source.
16 -{{/tip}}
12 +== Downloading Wonder Source from CVS ==
17 17  
18 -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 clone Wonder source to your computer.
14 +* 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.,,
15 +* Open a terminal shell and navigate to the directory
19 19  
20 -1. Clone the source repository from github into a new directory named "WonderSource".
17 +{{noformat}}
21 21  
22 -{{note title="Read Only"}}
23 -Note the URL shown here is the public read-only URL. Committers should use the SSH form of the URL for read-write
24 -{{/note}}
19 +cd ~/WonderLatest
25 25  
26 -{{code}}
27 -git clone git://github.com/projectwonder/wonder.git WonderSource
28 -{{/code}}
21 +{{/noformat}}
29 29  
30 -1. Navigate into the working copy root
23 +* Next perform initial checkout of Wonder source tree from CVS head using the following command. This creates a folder named Wonder
31 31  
32 -{{code}}
33 -cd WonderSource
34 -{{/code}}
25 +{{noformat}}
35 35  
36 -{{note title="WebObjects 5.3.3 Compatability"}}
37 -If you are still using old WebObjects 5.3.3, then you need to execute this git command to switch to the branch for WebObjects 5.3.3:{code}git checkout --track origin/Wonder_5_0_0_Legacy{code}
27 +cvs -z3 -d:pserver:anonymous@wonder.cvs.sourceforge.net:/cvsroot/wonder co -P Wonder
38 38  
39 -{{/note}}
29 +{{/noformat}}
40 40  
41 -== Build Frameworks ==
31 +== Build and Install Wonder ==
42 42  
43 -Assuming you now have a "cloned" copy of the Wonder source code, you can build the frameworks to the default (##/Roots##) with the following command:
44 -
45 -1. Build the frameworks from the "cloned" source.
46 -
47 -{{code}}
48 -ant frameworks
49 -{{/code}}
50 -
51 -1. Install the frameworks (this just copies the built frameworks from /Roots to the runtime Frameworks directory, usually at /Library/Frameworks)
52 -
53 -{{code}}
54 -sudo ant frameworks.install
55 -{{/code}}
56 -
57 -== Built Frameworks Upgrade Installation ==
58 -
59 -Assuming you already cloned and installed Wonder from source using the method outlined above, you can use the following procedure pull the latest changes into your local repository.
60 -
61 -1. Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
62 -
63 -{{code}}
64 -cd ~/Roots/
65 -{{/code}}
66 -
67 -1. Delete all installed frameworks whose names match the built frameworks in this Roots build folder
68 -
69 -{{code}}
70 -for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
71 -{{/code}}
72 -
73 -1. Navigate to the original Wonder source directory that you created above during initial source installation
74 -
75 -{{code}}
76 -cd /path/to/WonderSource
77 -{{/code}}
78 -
79 -1. Pull the changes you do not have and merge them with your local repository
80 -
81 -{{code}}
82 -git pull
83 -{{/code}}
84 -
85 -1. Clean, build and install the frameworks
86 -
87 -{{code}}
88 -
89 -ant clean
90 -ant frameworks
91 -sudo ant frameworks.install
92 -
93 -{{/code}}
94 -
95 -{{info}}
96 -
97 -If you have any trouble or errors due to your local repository getting hosed, then simply delete the entire local repository directory, the \~/Roots directory and just start over using the initial source clone and installation procedure outlined above.
98 -
99 -{{/info}}
100 -
101 -{{info value="Custom Development Enviroment File layout using Custom wolips.properties"}}
102 -
103 -If you have a custom wolips properties file for a specific workspace and you want to have a specific Wonder clone 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.
104 -
105 -For example:
106 -
107 -{code}
108 -$ cd my/special/purpose/clone/of/Wonder
109 -$ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
110 -{code}
111 -
112 -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.
113 -
114 -*Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
115 -{code}
116 -wo.external.root=/Users/mike/Developer/special/directory/Roots
117 -{code}
118 -
119 -*Tip:* A custom WebServer install directory can be specified to Wonder by adding the property 'wo.server.root' to the custom wolips properties file also.
120 -
121 -{{/info}}
33 +* Follow the instructions in the INSTALL.txt document in the Wonder directory