Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 215.1
edited by David Avendasora
on 2011/07/07 13:20
Change comment: There is no comment for this version
To version 212.1
edited by Kieran Kelleher
on 2010/08/14 19:52
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.kieran
Content
... ... @@ -1,93 +1,49 @@
1 -{{tip title="Now with more Git"}}
1 +== Introduction ==
2 2  
3 -As of March 25th, 2011 the Wonder source code is now maintained on [GitHub|https://github.com/] at [https://github.com/projectwonder]. You'll need to be familiar with the [Git|http://git-scm.com/] Source Code Management system. [Here's|WO: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 +Instead of downloading the Wonder binaries, working from the latest source code directly can have some advantages such as:
4 4  
5 -{{/tip}}
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
8 +* Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
6 6  
7 -== Why? ==
10 +== Downloading Wonder Source from Subversion ==
8 8  
9 -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:
12 +* 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//
13 +* Perform initial checkout of Wonder source tree from Subversion head using the following command. This checks out the source into the directory WonderLatest
10 10  
11 -* You'll learn a lot about WebObjects, EOF and Object-Oriented Patterns
12 -* Easily search and browse Project Wonder
13 -* Work with a specific revision of Project Wonder, which is key for teams, quality control and development cycles
14 -* Add logging statements to Project Wonder so you can better understand what it is doing when tracking down hard to find bugs
15 -* Discover the Many Hidden Treasures of Wonder™.
15 +{{noformat}}
16 16  
17 -== Download It ==
17 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder WonderSource
18 18  
19 -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.
19 +{{/noformat}}
20 20  
21 -1. h5. Clone the source repository from GitHub into a new directory named "WonderSource" or whatever you'd like.
21 +* As often as you prefer you can keep this up to date as follows:
22 22  
23 -{{code value="none"}}
24 -git clone git://github.com/projectwonder/wonder.git WonderSource
25 -{{/code}}
26 -
27 -If "git:~/~/" does not work for you then use "http:~/~/"
28 -
29 -{{note title="Wonder Committers"}}
30 -
31 -The URL above is the public, read-only URL.
32 -People with commit privileges for Project Wonder should use: *{{git@github.com:projectwonder/wonder.git}}*
33 -{warning}Do *not* change "git@..." to be your username.{warning}
34 -
35 -{{/note}}
36 -
37 -You should see output something like this:
38 -
39 39  {{noformat}}
40 40  
41 -Cloning into WonderSource...
42 -remote: Counting objects: 174269, done.
43 -remote: Compressing objects: 100% (57304/57304), done.
44 -remote: Total 174269 (delta 107374), reused 173934 (delta 107067)
45 -Receiving objects: 100% (174269/174269), 137.94 MiB | 8.29 MiB/s, done.
46 -Resolving deltas: 100% (107374/107374), done.
25 +cd /path/to/WonderSource
26 +svn up
47 47  
48 48  {{/noformat}}
49 49  
50 -1. h5. Navigate into the working copy root
30 +== Build and Install Wonder ==
51 51  
52 -{{code value="none"}}
53 -cd WonderSource
54 -{{/code}}
32 +* Follow the "Building with Ant" instructions in the BUILD.txt document in the Wonder directory
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: {code}git checkout --track origin/Wonder_5_0_0_Legacy{code}
58 -You should get output like this:
59 -{noformat}
60 -Branch Wonder_5_0_0_Legacy set up to track remote branch Wonder_5_0_0_Legacy from origin.
61 -Switched to a new branch 'Wonder_5_0_0_Legacy'
62 -{noformat}
34 +{{warning title="WebObjects 5.4.X Compatability"}}
63 63  
64 -{{/note}}
36 +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:
65 65  
66 -{{info}}
38 +ant \-Dwonder.patch=54 frameworks; sudo ant \-Dwonder.patch=54 frameworks.install
67 67  
68 -If you have any trouble or errors due to your local repository getting corrupted, simply delete the entire local repository (the {{\~/Roots}} directory) and start over using the same clone command above.
40 +{{/warning}}
69 69  
70 -{{/info}}
42 +== Concepts ==
71 71  
72 -== Use It ==
44 +This complete procedure results in you having
73 73  
74 -* h5. Use Wonder source code projects in your Eclipse workspace
75 -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: [[WONDER:Working with Wonder source in Eclipse]]
76 -
77 -{{note title="Ant Builds on your Development Machine"}}
78 -
79 -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|WO:Installing and Using the Hudson build server] locally 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* {color:#ff0000}{*}NOT{*}{color} *do this for you.*
80 -
81 -{{/note}}
82 -
83 -* h5. Build and Install Project Wonder Binary Frameworks
84 -For building and installing the Wonder Frameworks, please see the standard [[Building and Installing WO Frameworks with Ant>>WO:Building and Installing a Framework with Ant]] pages.
85 -
86 -{{note title="Using Both Binary and Source Code Frameworks on Your Development Machine"}}
87 -
88 -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.
89 -
90 -{{/note}}
91 -
92 -* h5. Build Project Wonder frameworks with Hudson/Jenkins
93 -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 [[WO:Installing and Configuring Jenkins Build Server]] page.
46 +* a Wonder directory with the whole Wonder source tree (directories, projects, frameworks, example apps, miscellaneous, etc.) inside.
47 +* The binary Wonder frameworks ("ant frameworks") will be installed in /Library/Frameworks.
48 +* If you ran "ant applications", they will be installed in ...
49 +* If you ran "ant examples", they will be installed in ...