Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 130.1
edited by David Avendasora
on 2011/04/26 13:21
on 2011/04/26 13:21
Change comment:
There is no comment for this version
To version 167.1
edited by Kieran Kelleher
on 2010/08/14 19:55
on 2010/08/14 19:55
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - GettingtheWonder SourceCode1 +Download Wonder Source, Build and Install - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. avendasora1 +XWiki.kieran - Content
-
... ... @@ -1,65 +1,50 @@ 1 - {{tiptitle="Now with moreGit"}}1 +== Introduction == 2 2 3 - Asof March 25th, 2011 theWondersourcecode is nowmaintainedon [GitHub|https://github.com/]at[https://github.com/projectwonder].You'll need tobe familiarwith the[Git|http://git-scm.com/]Source Code Management system. [Here's|WO:GettingStartedwithGit] a good placetostart.You will use Git toheckouta local copy of the repository(a "clone" in Git terms)allowingyou tohavedirect access totheWondersource.3 +Instead of downloading the Wonder binaries, working from the latest source code directly can have some advantages such as: 4 4 5 -{{/tip}} 6 - 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 - 9 -* You'll learn a lot about WebObjects, EOF and Object-Oriented Patterns 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 5 +* Ability to conveniently browse and search 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 12 12 * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs 13 -* Discover themanyHiddenTreasuresofWonder.9 +* Work with specific versions of Wonder in a project - good practice for quality control, especially for teams 14 14 15 -== Downloading == 11 +== Downloading Wonder Source from Subversion == 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. 13 +* 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// 14 +* Perform initial checkout of Wonder source tree from Subversion head using the following command. This checks out the source into the directory //WonderSource//, automatically creating //WonderSource// if it does not exist. 18 18 19 - 1. h5. Clone the source repositoryfrom GitHub into a new directory named "WonderSource" or whatever you'd like.16 +{{noformat}} 20 20 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}} 18 +svn co http://wonder.svn.sourceforge.net/svnroot/wonder/trunk/Wonder WonderSource 24 24 25 -{{code value="none"}} 26 -git clone git://github.com/projectwonder/wonder.git WonderSource 27 -{{/code}} 20 +{{/noformat}} 28 28 29 - Youshouldsee outputsomethinglike this:22 +* As often as you prefer you can keep this up to date as follows: 30 30 31 31 {{noformat}} 32 32 33 -Cloning into WonderSource... 34 -remote: Counting objects: 174269, done. 35 -remote: Compressing objects: 100% (57304/57304), done. 36 -remote: Total 174269 (delta 107374), reused 173934 (delta 107067) 37 -Receiving objects: 100% (174269/174269), 137.94 MiB | 8.29 MiB/s, done. 38 -Resolving deltas: 100% (107374/107374), done. 26 +cd /path/to/WonderSource 27 +svn up 39 39 40 40 {{/noformat}} 41 41 42 - 1.h5.Navigateintothe working copyroot31 +== Build and Install Wonder == 43 43 44 -{{code value="none"}} 45 -cd WonderSource 46 -{{/code}} 33 +* Follow the "Building with Ant" instructions in the BUILD.txt document in the Wonder directory 47 47 48 -{{note title="WebObjects 5.3.3 Compatability"}} 49 -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} 50 -You should get output like this: 51 -{noformat} 52 -Branch Wonder_5_0_0_Legacy set up to track remote branch Wonder_5_0_0_Legacy from origin. 53 -Switched to a new branch 'Wonder_5_0_0_Legacy' 54 -{noformat} 35 +{{warning title="WebObjects 5.4.X Compatability"}} 55 55 56 - {{/note}}37 +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: 57 57 58 -1. h5. Build and Install 59 -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. 39 +ant \-Dwonder.patch=54 frameworks; sudo ant \-Dwonder.patch=54 frameworks.install 60 60 61 -{{in fo}}41 +{{/warning}} 62 62 63 - Ifyou have any trouble or errors due to your local repository getting corrupted,simplydelete the entire local repository (the {{\~/Roots}} directory) and start over using this source clone procedure.43 +== Concepts == 64 64 65 -{{/info}} 45 +This complete procedure results in you having 46 + 47 +* a Wonder directory with the whole Wonder source tree (directories, projects, frameworks, example apps, miscellaneous, etc.) inside. 48 +* The binary Wonder frameworks ("ant frameworks") will be installed in /Library/Frameworks. 49 +* If you ran "ant applications", they will be installed in ... 50 +* If you ran "ant examples", they will be installed in ...