Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 118.1
edited by David Avendasora
on 2011/04/25 14:34
Change comment: There is no comment for this version
To version 117.1
edited by David Avendasora
on 2011/04/25 10:30
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, Install and Upgrade
Content
... ... @@ -9,131 +9,68 @@
9 9  * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
10 10  * Discover the many Hidden Treasures of Wonder.
11 11  
12 -== Downloading ==
12 +== Source Frameworks Initial Installation ==
13 13  
14 14  {{tip title="Now with more Git"}}
15 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 16  {{/tip}}
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.
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 own hard-drive.
19 19  
20 -1. h5. Clone the source repository from github into a new directory named "WonderSource".
20 +1. Clone the source repository from github into a new directory named "WonderSource".
21 21  
22 22  {{note title="Read Only"}}
23 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 24  {{/note}}
25 25  
26 -{{code value="none"}}
26 +{{code}}
27 27  git clone git://github.com/projectwonder/wonder.git WonderSource
28 28  {{/code}}
29 29  
30 -You should see output something like this:
30 +1. Navigate into the working copy root
31 31  
32 -{{noformat}}
33 -
34 -Cloning into WonderSource...
35 -remote: Counting objects: 174269, done.
36 -remote: Compressing objects: 100% (57304/57304), done.
37 -remote: Total 174269 (delta 107374), reused 173934 (delta 107067)
38 -Receiving objects: 100% (174269/174269), 137.94 MiB | 8.29 MiB/s, done.
39 -Resolving deltas: 100% (107374/107374), done.
40 -
41 -{{/noformat}}
42 -
43 -1. h5. Navigate into the working copy root
44 -
45 -{{code value="none"}}
32 +{{code}}
46 46  cd WonderSource
47 47  {{/code}}
48 48  
49 49  {{note title="WebObjects 5.3.3 Compatability"}}
50 -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}
51 -You should get output like this:
52 -{noformat}
53 -Branch Wonder_5_0_0_Legacy set up to track remote branch Wonder_5_0_0_Legacy from origin.
54 -Switched to a new branch 'Wonder_5_0_0_Legacy'
55 -{noformat}
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}
56 56  
57 57  {{/note}}
58 58  
59 -== Building ==
41 +1. Build the frameworks from the source.
60 60  
61 -In general, it is recommended that you use Hudson/Jenkins to build your WebObjects applications, but it is not required. You can build either from the Terminal as outlined below, or from within Eclipse.
62 -
63 -{{tip title="Pro Tip"}}
64 -If you use Hudson/Jenkins to build your WebObjects applications, then you do not need to actually build or install the Project Wonder frameworks on your development machine, just having the individual Wonder source code projects open in your eclipse workspace is sufficient.
65 -{{/tip}}
66 -
67 -{{note title="Requires WebObjects"}}
68 -
69 -These build instructions require the WebObjects frameworks to already be installed in the normal location:
70 -* Mac OS X: {{/System/Library/Framworks/}}
71 -* Linux: {{/Library/Frameworks}}
72 -
73 -Otherwise you will get compiler errors like this:
74 -{noformat}
75 -[wocompile] /Wonder/WonderGit/WonderSource/Frameworks/Core/JavaWOExtensions/Sources/com/webobjects/woextensions/JSAlertPanel.java:10:
76 - package com.webobjects.appserver does not exist
77 -[wocompile] import com.webobjects.appserver.WOContext;
78 -{noformat}
79 -
80 -{{/note}}
81 -
82 -You can build the Wonder frameworks from the source code you just cloned to the default (##/Roots##) directory with the following command:
83 -
84 -===== Build the frameworks from the "cloned" source. =====
85 -
86 -{{code value="none"}}
43 +{{code}}
87 87  ant frameworks
88 88  {{/code}}
89 89  
90 -== Installing ==
47 +1. Install the frameworks (this just copies the built frameworks from /Roots to the runtime Frameworks directory, usually at /Library/Frameworks)
91 91  
92 -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.
93 -
94 -===== Install the frameworks =====
95 -
96 -{{code value="none"}}
49 +{{code}}
97 97  sudo ant frameworks.install
98 98  {{/code}}
99 99  
100 -This copies the built frameworks from ##/Roots## to the runtime Frameworks directory:
53 +== Source Frameworks Upgrade Installation ==
101 101  
102 -* Mac OS X: ##/Library/Framworks/##
103 -* Linux: ##/Local/Library/Frameworks##
55 +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.
104 104  
105 -You can combine the build and install steps by simply executing this Ant command:
57 +{{code title="Updating your Source"}}
106 106  
107 -{{code value="none"}}
108 -sudo ant frameworks frameworks.install
109 -{{/code}}
110 -
111 -== Upgrading ==
112 -
113 -This will clean out the existing versions of the frameworks. This isn't strictly necessary, you could just re-install over the top of the old frameworks, but deleting then manually copying over the new ones will clean up any old frameworks that are no longer included in the standard build.
114 -
115 -1. h5. Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
116 -
117 -{{code value="none"}}
59 +# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
118 118  cd ~/Roots/
119 -{{/code}}
120 120  
121 -1. h5. Delete all installed frameworks whose names match the built frameworks in this Roots build folder
122 -
123 -{{code value="none"}}
62 +# Delete all installed frameworks whose names match the built frameworks in this Roots build folder
124 124  for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
125 -{{/code}}
126 126  
127 -1. h5. Navigate to the original Wonder source directory that you created above during initial source installation
128 -
129 -{{code value="none"}}
65 +# Navigate to the original Wonder source directory that you created above during initial source installation
130 130  cd /path/to/WonderSource
131 -{{/code}}
132 132  
133 -1. h5. Pull the changes you do not have and merge them with your local repository
134 -
135 -{{code value="none"}}
68 +# Pull the changes you do not have and merge them with your local repository
136 136  git pull
70 +
71 +# Clean, build and install the frameworks
72 +ant clean; ant frameworks; sudo ant frameworks.install
73 +
137 137  {{/code}}
138 138  
139 139  {{info}}
... ... @@ -148,15 +148,15 @@
148 148  
149 149  For example:
150 150  
151 -{code:none}
152 -cd my/special/purpose/clone/of/Wonder
153 -ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
154 154  {code}
89 +$ cd my/special/purpose/clone/of/Wonder
90 +$ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
91 +{code}
155 155  
156 156  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.
157 157  
158 158  *Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example
159 -{code:none}
96 +{code}
160 160  wo.external.root=/Users/mike/Developer/special/directory/Roots
161 161  {code}
162 162