Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 233.2
edited by Pascal Robert
on 2023/11/13 11:54
Change comment: Updated the relative links.
To version 209.1
edited by franc
on 2010/09/13 17:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Getting the Wonder Source Code
1 +Download Wonder Source, Build and Install
Parent
... ... @@ -1,1 +1,0 @@
1 -Getting Started
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.probert
1 +XWiki.franc
Tags
... ... @@ -1,1 +1,0 @@
1 -favourite
Content
... ... @@ -1,103 +1,110 @@
1 -{{tip title="Now with more Git"}}
2 -As of May 21th, 2013 the Wonder source code is now maintained on [[GitHub>>url:https://github.com/||shape="rect"]] at [[https:~~/~~/github.com/wocommunity/wonder>>url:https://github.com/wocommunity/wonder||shape="rect"]]. You'll need to be familiar with the [[Git>>url:http://git-scm.com/||shape="rect"]] Source Code Management system. [[Here's>>doc:Getting Started with Git]] a good place to start. You will use Git to checkout a local copy of the repository (a "clone" in Git terms) allowing you to have direct access to the Wonder source.
3 -{{/tip}}
1 +== Introduction ==
4 4  
5 -== Why? ==
3 +Instead of downloading the Wonder binaries, working from the latest source code directly can have some advantages such as:
6 6  
7 -Instead of constantly re-downloading and installing the latest Project Wonder binaries you should work directly with the latest source code. It has several advantages including:
5 +* Learn very much about WebObjects and EOF (and java dev styles?)
6 +* Easily browse and search the source
7 +* Work with a specific svn version (teams, quality control, development cycles)
8 +* Provide opportunities to submit patches for bug fixes or enhancements
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
8 8  
9 -* You'll learn a lot about WebObjects, EOF and Object-Oriented Patterns
10 -* Easily search and browse Project Wonder
11 -* Work with a specific revision of Project Wonder, which is key for teams, quality control and development cycles
12 -* Add logging statements to Project Wonder so you can better understand what it is doing when tracking down hard to find bugs
13 -* Discover the Many Hidden Treasures of Wonder™.
12 +== Source Frameworks Initial Installation ==
14 14  
15 -== Download It! ==
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 the build and installation commands are slighly different for WebObjects 5.4.X. So procedures for both WebObjects 5.4.X and 5.3.X are shown below. Pick you poison:
16 16  
17 -Open a terminal and navigate to a directory where you want to maintain a source "working copy" and just use the following commands to clone Wonder source to your computer.
16 +{{code title="Procedure for WebObjects 5.4.X"}}
18 18  
19 -1. (((
20 -===== Clone the source repository from GitHub into a new directory named "WonderSource" or whatever you'd like. =====
18 +# Checkout the source from subversion repository into a new directory named "WonderSource"
19 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision <ARG> WonderSource
21 21  
22 -{{code 0="none"}}
23 -git clone git://github.com/wocommunity/wonder.git WonderSource
24 -{{/code}}
21 +# Navigate into the working copy root
22 +cd WonderSource
25 25  
26 -If "git:~/~/" does not work for you then use "http:~/~/"
24 +# Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
25 +ant -DWonder.patch=54 frameworks
27 27  
28 -{{note title="Wonder Committers"}}
29 -The URL above is the public, read-only URL.
30 - People with commit privileges for Project Wonder should use: **git@github.com:wocommunity/wonder.git**
27 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
28 +# the runtime Frameworks directory, usually at /Library/Framrworks
29 +sudo ant -DWonder.patch=54 frameworks.install
31 31  
32 -{{warning}}
33 -Do **not** change "git@..." to be your username.
34 -{{/warning}}
35 -{{/note}}
31 +{{/code}}
36 36  
37 -You should see output something like this:
33 +{{code title="Procedure for WebObjects 5.3.X"}}
38 38  
39 -{{noformat}}
40 -Cloning into WonderSource...
41 -remote: Counting objects: 174269, done.
42 -remote: Compressing objects: 100% (57304/57304), done.
43 -remote: Total 174269 (delta 107374), reused 173934 (delta 107067)
44 -Receiving objects: 100% (174269/174269), 137.94 MiB | 8.29 MiB/s, done.
45 -Resolving deltas: 100% (107374/107374), done.
35 +# Checkout the source from subversion repository into a new directory named "WonderSource"
36 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder --revision <ARG> WonderSource
46 46  
47 -{{/noformat}}
48 -)))
49 -1. (((
50 -===== Navigate into the working copy root =====
51 -
52 -{{code 0="none"}}
38 +# Navigate into the working copy root
53 53  cd WonderSource
54 -{{/code}}
55 55  
56 -{{note title="WebObjects 5.3.3 Compatability"}}
57 -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:
41 +# Build the frameworks from the source (BTW, they get built into a directory named Roots in your home dir)
42 +ant frameworks
58 58  
59 -{{code}}
60 -git checkout --track origin/Wonder_5_0_0_Legacy
44 +# Install the frameworks (this just copies the built frameworks from ~/Roots to
45 +# the runtime Frameworks directory, usually at /Library/Framrworks
46 +sudo ant frameworks.install
47 +
61 61  {{/code}}
62 62  
63 -You should get output like this:
50 +== Source Frameworks Upgrade Installation ==
64 64  
65 -{{noformat}}
66 -Branch Wonder_5_0_0_Legacy set up to track remote branch Wonder_5_0_0_Legacy from origin.
67 -Switched to a new branch 'Wonder_5_0_0_Legacy'
52 +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.
68 68  
69 -{{/noformat}}
70 -{{/note}}
71 -)))
54 +{{code title="Procedure for WebObjects 5.4.X"}}
72 72  
73 -{{info}}
74 -If you have any trouble or errors due to your local repository getting corrupted, simply delete the entire local repository (the {{code language="none"}}WonderSource{{/code}} directory) and start over using the same clone command above.
75 -{{/info}}
56 +# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
57 +cd ~/Roots/
76 76  
77 -== Use It! ==
59 +# Delete all installed frameworks whose names match the built frameworks in this Roots build folder
60 +$ for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
78 78  
79 -* (((
80 -===== Use Wonder source code projects in your Eclipse workspace =====
62 +# Navigate to the original Wonder source directory that you created above during initial source installation
63 +$ cd /path/to/WonderSource
81 81  
82 -The best way to make use of Project Wonder is obviously to import the source code projects directly into your Eclipse workspace. Why would you be reading this page if that isn't what you are trying to do?! Detailed instructions are here: [[doc:WEB.Working with Wonder source in Eclipse]]
65 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn
66 +# repository version instead of the term 'HEAD', for example 11272
67 +svn update --force --accept theirs-full --revision HEAD
83 83  
84 -{{note title="Ant Builds on your Development Machine"}}
85 -WOlips' "Incremental Builder" is an incredibly helpful feature during development, but it does things that the Ant deployment build does not do. If you are **either** using WOLips to build your WebObjects Applications (//WOLips Ant Tools > Install//) **or** are [[running Hudson/Jenkins locally>>doc:documentation.Installing and Configuring Jenkins]] to do it, you **must** also build and install your workspace's Frameworks that your Application depends upon – including your own, Project Wonder's and any others. **The standard Ant build does** (% style="color: rgb(255,0,0);" %)**NOT**(%%) **do this for you.**
86 -{{/note}}
87 -)))
69 +# Clean the previous build artifacts
70 +ant -Dwonder.patch=54 clean
88 88  
89 -* (((
90 -===== Build and Install Project Wonder Binary Frameworks =====
72 +# Build from the latest source
73 +ant -Dwonder.patch=54 frameworks
91 91  
92 -For building and installing the Wonder Frameworks, please see the standard [[Building and Installing WO Frameworks with Ant>>doc:documentation.Building and Installing a Framework with Ant]] pages.
75 +# Install the latest built frameworks
76 +sudo ant -Dwonder.patch=54 frameworks.install
93 93  
94 -{{note title="Using Both Binary and Source Code Frameworks on Your Development Machine"}}
95 -If you have both Source Code projects and the built, Binary Frameworks installed, you need to make sure you build all source code frameworks that your project depends upon first. //The standard Ant build does not do this for you.// Ant builds only use binary frameworks so if the installed frameworks are not up to date your Ant build could fail, or worse, succeed but contain run-time errors.
96 -{{/note}}
97 -)))
78 +{{/code}}
98 98  
99 -* (((
100 -===== Build Project Wonder frameworks with Hudson/Jenkins =====
80 +{{code title="Procedure for WebObjects 5.3.X"}}
101 101  
102 -The ideal way to build WebObjects frameworks and applications is to use a "Continuous Integration Server" or "Build Server" like Hudson or Jenkins. This allows you to automate the often complex process of building WebObjects projects that have several dependencies on frameworks. Instructions on how to setup a Hudson/Jenkins server is are available on the [[doc:documentation.Installing and Configuring Jenkins]] page.
103 -)))
82 +# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
83 +cd ~/Roots/
84 +
85 +# Delete all installed frameworks whose names match the built frameworks in this Roots build folder
86 +$ for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
87 +
88 +# Navigate to the original Wonder source directory that you created above during initial source installation
89 +$ cd /path/to/WonderSource
90 +
91 +# Update the source to the HEAD revision (aka latest). You can also use a specific svn
92 +# repository version instead of the term 'HEAD', for example 11272
93 +svn update --force --accept theirs-full --revision HEAD
94 +
95 +# Clean the previous build artifacts
96 +ant clean
97 +
98 +# Build from the latest source
99 +ant frameworks
100 +
101 +# Install the latest built frameworks
102 +sudo frameworks.install
103 +
104 +{{/code}}
105 +
106 +{{info}}
107 +
108 +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.
109 +
110 +{{/info}}