Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 111.1
edited by David Avendasora
on 2011/06/16 18:24
Change comment: There is no comment for this version
To version 131.1
edited by David Avendasora
on 2011/04/26 13:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,36 +4,28 @@
4 4  
5 5  {{/tip}}
6 6  
7 -== Why? ==
7 +Instead of constantly re-downloading and installing the latest Wonder binaries you should work directly with the latest source code. It has several advantages including:
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:
10 -
11 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™.
10 +* Easily search, browse and even modify and improve Wonder
11 +* Work with a specific revision, which is key for teams, quality control and development cycles
12 +* Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs
13 +* Discover the many Hidden Treasures of Wonder.
16 16  
17 -== Download It ==
15 +== Downloading ==
18 18  
19 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.
20 20  
21 21  1. h5. Clone the source repository from GitHub into a new directory named "WonderSource" or whatever you'd like.
22 22  
21 +{{note title="Read Only"}}
22 +Note the URL shown here is the public read-only URL. Committers should use the SSH form of the URL for read-write
23 +{{/note}}
24 +
23 23  {{code value="none"}}
24 24  git clone git://github.com/projectwonder/wonder.git WonderSource
25 25  {{/code}}
26 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 37  You should see output something like this:
38 38  
39 39  {{noformat}}
... ... @@ -63,31 +63,11 @@
63 63  
64 64  {{/note}}
65 65  
66 -{{info}}
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.
69 -
70 -{{/info}}
71 -
72 -== Use It ==
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
58 +1. h5. Build and Install
84 84  For building and installing the Wonder Frameworks, please see the standard [[Building and Installing WO Frameworks with Ant>>WO:Building and Installing a WO Framework with Ant]] pages.
85 85  
86 -{{note title="Using Both Binary and Source Code Frameworks on Your Development Machine"}}
61 +{{info}}
87 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.
63 +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 this source clone procedure.
89 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 Using Jenkins and Hudson Build Servers]] page.
65 +{{/info}}