Last modified by Bastian Triller on 2013/10/05 10:40

From version 117.1
edited by David Avendasora
on 2011/04/25 10:30
Change comment: There is no comment for this version
To version 142.1
edited by Kieran Kelleher
on 2010/09/27 17:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.kieran
Content
... ... @@ -2,59 +2,58 @@
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)
5 +* Learn very much about WebObjects and EOF (and java dev styles?)
6 6  * Easily browse and search the source
7 -* Work with a specific source control version (teams, quality control, development cycles)
7 +* Work with a specific svn version (teams, quality control, development cycles)
8 8  * Provide opportunities to submit patches for bug fixes or enhancements
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.
10 +* Discover the many Hidden Treasures of Wonder
11 11  
12 12  == Source Frameworks Initial Installation ==
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}}
14 +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 as of repository version 11387 (Sep 27, 2010) the Wonder repository URL is the only difference between the Wonder source procedure for WebObjects 5.3.3 and WebObjects 5.4.3 installation. For your copy/paste convenience, the full procedures for both WebObjects 5.4.X and 5.3.X are shown below. WebObjects 5.4.3 and the Wonder branch for same is recommended and is where the most features are expected to be found.
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 own hard-drive.
16 +{{code title="Procedure for WebObjects 5.4.X"}}
19 19  
20 -1. Clone the source repository from github into a new directory named "WonderSource".
18 +# Checkout the source from subversion repository into a new directory named "WonderSource"
19 +# Note instead of HEAD, you can use a specific svn version number if you want
20 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/branches/Wonder_5_0_0_WebObjects_5_4_Branch/Wonder --revision HEAD WonderSource
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}}
22 +# Navigate into the working copy root
23 +cd WonderSource
25 25  
26 -{{code}}
27 -git clone git://github.com/projectwonder/wonder.git WonderSource
28 -{{/code}}
25 +# Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
26 +ant frameworks
29 29  
30 -1. Navigate into the working copy root
28 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
29 +# the runtime Frameworks directory, usually at /Library/Frameworks)
30 +sudo ant frameworks.install
31 31  
32 -{{code}}
33 -cd WonderSource
34 34  {{/code}}
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}
34 +{{code title="Procedure for WebObjects 5.3.X"}}
38 38  
39 -{{/note}}
36 +# Checkout the source from subversion repository into a new directory named "WonderSource"
37 +# Note instead of HEAD, you can use a specific svn version number if you want
38 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision HEAD WonderSource
40 40  
41 -1. Build the frameworks from the source.
40 +# Navigate into the working copy root
41 +cd WonderSource
42 42  
43 -{{code}}
43 +# Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
44 44  ant frameworks
45 -{{/code}}
46 46  
47 -1. Install the frameworks (this just copies the built frameworks from /Roots to the runtime Frameworks directory, usually at /Library/Frameworks)
48 -
49 -{{code}}
46 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
47 +# the runtime Frameworks directory, usually at /Library/Frameworks)
50 50  sudo ant frameworks.install
49 +
51 51  {{/code}}
52 52  
53 53  == Source Frameworks Upgrade Installation ==
54 54  
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.
54 +Assuming you already installed Wonder from source using the method outlined above, you can use the following procedure to upgrade to a newer, or just different version. Note that the procedure for both WebObjects 5.4.X and 5.3.X are outlined below. They are the same except for the last 3 ant commands.
56 56  
57 -{{code title="Updating your Source"}}
56 +{{code title="Procedure for WebObjects 5.4.X"}}
58 58  
59 59  # Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
60 60  cd ~/Roots/
... ... @@ -65,8 +65,9 @@
65 65  # Navigate to the original Wonder source directory that you created above during initial source installation
66 66  cd /path/to/WonderSource
67 67  
68 -# Pull the changes you do not have and merge them with your local repository
69 -git pull
67 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn
68 +# repository version instead of the term 'HEAD', for example 11272
69 +svn update --force --accept theirs-full --revision HEAD
70 70  
71 71  # Clean, build and install the frameworks
72 72  ant clean; ant frameworks; sudo ant frameworks.install
... ... @@ -73,20 +73,41 @@
73 73  
74 74  {{/code}}
75 75  
76 +{{code title="Procedure for WebObjects 5.3.X"}}
77 +
78 +# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
79 +cd ~/Roots/
80 +
81 +# Delete all installed frameworks whose names match the built frameworks in this Roots build folder
82 +for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
83 +
84 +# Navigate to the original Wonder source directory that you created above during initial source installation
85 +cd /path/to/WonderSource
86 +
87 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn
88 +# repository version instead of the term 'HEAD', for example 11272
89 +svn update --force --accept theirs-full --revision HEAD
90 +
91 +# Clean, build and install the frameworks
92 +ant clean; ant frameworks; sudo ant frameworks.install
93 +
94 +
95 +{{/code}}
96 +
76 76  {{info}}
77 77  
78 -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.
99 +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.
79 79  
80 80  {{/info}}
81 81  
82 82  {{info value="Custom Development Enviroment File layout using Custom wolips.properties"}}
83 83  
84 -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.
105 +If you have a custom wolips properties file for a specific workspace and you want to have a specific Wonder source working copy 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.
85 85  
86 86  For example:
87 87  
88 88  {code}
89 -$ cd my/special/purpose/clone/of/Wonder
110 +$ cd my/special/purpose/working/copy/of/Wonder
90 90  $ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties
91 91  {code}
92 92  
... ... @@ -97,6 +97,6 @@
97 97  wo.external.root=/Users/mike/Developer/special/directory/Roots
98 98  {code}
99 99  
100 -*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.
121 +*Tip:* A custom WebServer install directory can be specified to Wonder by adding the property 'wo.server.root' to the custom wilips properties file also.
101 101  
102 102  {{/info}}