Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 113.1
edited by David Avendasora
on 2011/04/25 10:24
on 2011/04/25 10:24
Change comment:
There is no comment for this version
To version 126.1
edited by Paul Hoadley
on 2011/03/27 03:10
on 2011/03/27 03:10
Change comment:
Added a couple of hyperlinks.
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.a vendasora1 +XWiki.paulh - Content
-
... ... @@ -11,43 +11,42 @@ 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 get a local copy of the repository (a "clone" in Git terms) allowing us to have direct access to the Wonder source. 16 -{{/tip}} 14 +As of March 25th, 2011, Wonder is maintained on [[GitHub>>https://github.com/]]. So [[Git>>http://git-scm.com/]] is what we use to get a local clone of the repository allowing us to directly use Wonder source. 17 17 18 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. 19 19 20 -1. Clone the source repository from github into a new directory named "WonderSource". 21 -1. Note the URL shown here is the public read-only URL. Committers should use the SSH form of the URL for read-write 18 +{{code title="Cloning Project Wonder for the First Time"}} 22 22 23 -{{code}} 20 +# Clone the source repository from github into a new directory named "WonderSource". 21 +# Note the URL shown here is the public read-only URL. Committers should use the SSH form of the URL for read-write 24 24 git clone git://github.com/projectwonder/wonder.git WonderSource 25 -{{/code}} 26 26 27 -1. Navigate into the working copy root 28 - 29 -{{code}} 24 +# Navigate into the working copy root 30 30 cd WonderSource 31 -{{/code}} 32 32 33 - {{note title="WebObjects 5.3.3Compatability"}}34 - If youare stillusing old WebObjects 5.3.3, then youneedtoexecutethis git commandtoswitch to the branchforWebObjects5.3.3:{code}gitcheckout--trackorigin/Wonder_5_0_0_Legacy{code}27 +# If you are still using old WebObjects 5.3.3, then you need to execute one git command at this point 28 +# before you build Wonder to switch to the branch that is source-compatible with WO 5.3.3. See the tip at the bottom of the page. 35 35 36 -{{/note}} 30 +# Build the frameworks from the source (Assumes you are using WebObjects 5.4.3, 31 +# which is currently compatible with 'master' branch. See note below for WebObjects 5.3.3 compatible install) 32 +ant frameworks 37 37 38 -1. Build the frameworks from the source. 34 +# Install the frameworks (this just copies the built frameworks from ~/Roots to 35 +# the runtime Frameworks directory, usually at /Library/Frameworks) 36 +sudo ant frameworks.install 39 39 40 -{{code}} 41 -ant frameworks 42 42 {{/code}} 43 43 44 - 1. Install theframeworks(this just copies the built frameworks from /Rootstothe runtime Frameworks directory, usually at /Library/Frameworks)40 +{{info value="Legacy WebObjects 5.3.3 Compatability"}} 45 45 46 -{{code}} 47 -sudo ant frameworks.install 48 -{{/code}} 42 +If you are still stuck on WebObjects 5.3.3, for whatever reason, then you need to checkout and switch to the Wonder_5_0_0_Legacy branch *before* you build (before you run 'ant frameworks'). And this is *much* easier with git than it used to be with subversion. Just one command: 43 + 44 +{code} 45 +git checkout --track origin/Wonder_5_0_0_Legacy 46 +{code} 47 + 49 49 50 - œ49 +{{/info}} 51 51 52 52 == Source Frameworks Upgrade Installation == 53 53 ... ... @@ -72,6 +72,8 @@ 72 72 73 73 {{/code}} 74 74 74 + 75 + 75 75 {{info}} 76 76 77 77 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.