Skip to Content
Last modified by Bastian Triller on 2013/10/05 10:40
From version 101.1
edited by David Avendasora
on 2011/06/13 21:41
Change comment: There is no comment for this version
To version 106.1
edited by David Avendasora
on 2011/07/07 13:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,14 +20,20 @@
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  
23 -{{note title="Read Only"}}
24 -Note the URL shown here is the public read-only URL. Committers should use the SSH form of the URL for read-write
25 -{{/note}}
26 -
27 27  {{code value="none"}}
28 28  git clone git://github.com/projectwonder/wonder.git WonderSource
29 29  {{/code}}
30 30  
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 +
31 31  You should see output something like this:
32 32  
33 33  {{noformat}}
... ... @@ -70,12 +70,12 @@
70 70  
71 71  {{note title="Ant Builds on your Development Machine"}}
72 72  
73 -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.*
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.*
74 74  
75 75  {{/note}}
76 76  
77 77  * h5. Build and Install Project Wonder Binary Frameworks
78 -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.
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.
79 79  
80 80  {{note title="Using Both Binary and Source Code Frameworks on Your Development Machine"}}
81 81  
... ... @@ -84,4 +84,4 @@
84 84  {{/note}}
85 85  
86 86  * h5. Build Project Wonder frameworks with Hudson/Jenkins
87 -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.
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 Jenkins]] page.