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 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - DownloadWonder Source,Build, Install and Upgrade1 +Getting the Wonder Source Code - Content
-
... ... @@ -1,101 +1,65 @@ 1 - ==Introduction==1 +{{tip title="Now with more Git"}} 2 2 3 - Instead ofdownloading theWonder binaries,workingfromthelatest source codedirectly can have someadvantagessuch as: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. 4 4 5 -* Learn a lot about WebObjects and EOF (and Java development styles) 6 -* Easily browse and search the source 7 -* Work with a specific source control version (teams, quality control, development cycles) 8 -* Provide opportunities to submit patches for bug fixes or enhancements 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 9 9 * Add logging statements in Wonder source so you can better understand what is going when tracking down hard to find bugs 10 10 * Discover the many Hidden Treasures of Wonder. 11 11 12 -== Source Frameworks InitialInstallation ==15 +== Downloading == 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}} 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. 17 17 18 - Openaterminalandnavigatetoa directorywhere you want tomaintain a source"working copy"andjust usethe followingeasy-peasycommandstoclone Wondersourcetoyourownhard-drive.19 +1. h5. Clone the source repository from GitHub into a new directory named "WonderSource" or whatever you'd like. 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 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}} 22 22 23 -{{code}} 25 +{{code value="none"}} 24 24 git clone git://github.com/projectwonder/wonder.git WonderSource 25 25 {{/code}} 26 26 27 - 1.Navigateintoheworkingcopyroot29 +You should see output something like this: 28 28 29 -{{code}} 30 -cd WonderSource 31 -{{/code}} 31 +{{noformat}} 32 32 33 -{{note title="WebObjects 5.3.3 Compatability"}} 34 -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} 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. 35 35 36 -{{/not e}}40 +{{/noformat}} 37 37 38 -1. Build theframeworksfromthesource.42 +1. h5. Navigate into the working copy root 39 39 40 -{{code}} 41 - antframeworks44 +{{code value="none"}} 45 +cd WonderSource 42 42 {{/code}} 43 43 44 -1. Install the frameworks (this just copies the built frameworks from /Roots to the runtime Frameworks directory, usually at /Library/Frameworks) 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} 45 45 46 -{{code}} 47 -sudo ant frameworks.install 48 -{{/code}} 56 +{{/note}} 49 49 50 -œ 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. 51 51 52 -== Source Frameworks Upgrade Installation == 53 - 54 -Assuming you already cloned and installed Wonder from source using the method outlined above, you can use the following procedure pull the latest changes into your local repository. 55 - 56 -{{code title="Updating your Source"}} 57 - 58 -# Navigate to the Roots directory that was automatically created by the initial Source installation procedure above 59 -cd ~/Roots/ 60 - 61 -# Delete all installed frameworks whose names match the built frameworks in this Roots build folder 62 -for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done 63 - 64 -# Navigate to the original Wonder source directory that you created above during initial source installation 65 -cd /path/to/WonderSource 66 - 67 -# Pull the changes you do not have and merge them with your local repository 68 -git pull 69 - 70 -# Clean, build and install the frameworks 71 -ant clean; ant frameworks; sudo ant frameworks.install 72 - 73 -{{/code}} 74 - 75 75 {{info}} 76 76 77 -If you have any trouble or errors due to your local repository getting hosed,thensimply delete the entire local repositorydirectory, the \~/Roots directory andjuststart over using theinitialsource cloneand installationprocedureoutlined above.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. 78 78 79 79 {{/info}} 80 - 81 -{{info value="Custom Development Enviroment File layout using Custom wolips.properties"}} 82 - 83 -If you have a custom wolips properties file for a specific workspace and you want to have a specific Wonder clone for that workspace, you can simply link your custom wolips properties file to a soft link named build.properties in the working copy root directory. The Wonder build script will supersede all other filesystem layout poperties with the properties in that file. 84 - 85 -For example: 86 - 87 -{code} 88 -$ cd my/special/purpose/clone/of/Wonder 89 -$ ln -s ~/Library/Application\ Support/WOLips/wolips.custom.properties build.properties 90 -{code} 91 - 92 -An example of where this approach might be used would be when you have different projects (perhaps in a specially designated workspace) that use a specific version of WebObjects and a specific version or branch of Wonder. 93 - 94 -*Tip:* Specify a custom build directory for Wonder by adding the property 'wo.external.root' to the custom wolips properties file, for example 95 -{code} 96 -wo.external.root=/Users/mike/Developer/special/directory/Roots 97 -{code} 98 - 99 -*Tip:* A custom WebServer install directory can be specified to Wonder by adding the property 'wo.server.root' to the custom wolips properties file also. 100 - 101 -{{/info}}