Changes for page Getting the Wonder Source Code
Last modified by Bastian Triller on 2013/10/05 10:40
From version 124.1
edited by David Avendasora
on 2011/04/25 14:40
on 2011/04/25 14:40
Change comment:
There is no comment for this version
To version 119.1
edited by David Avendasora
on 2011/04/25 14:34
on 2011/04/25 14:34
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -58,10 +58,10 @@ 58 58 59 59 == Building == 60 60 61 -In general, it is recommended that you use Hudson/Jenkins to build your WebObjects frameworks and applications, but it is not required. You can build either from the Terminal as outlined below, or from within Eclipsedirectly.61 +In general, it is recommended that you use Hudson/Jenkins to build your WebObjects applications, but it is not required. You can build either from the Terminal as outlined below, or from within Eclipse. 62 62 63 63 {{tip title="Pro Tip"}} 64 -If you use Hudson/Jenkins to build your WebObjects applications, then you do not need to actually build or install the Project Wonder frameworks on your development machine, just having the individual Wonder source code projects open in your eclipse workspace is sufficient. Your Hudson/Jenkins server will need the built frameworks installed. See the [Hudson/Jenkins Page|WO:Installing and Using the Hudson build server] for more information.64 +If you use Hudson/Jenkins to build your WebObjects applications, then you do not need to actually build or install the Project Wonder frameworks on your development machine, just having the individual Wonder source code projects open in your eclipse workspace is sufficient. 65 65 {{/tip}} 66 66 67 67 {{note title="Requires WebObjects"}} ... ... @@ -112,36 +112,30 @@ 112 112 113 113 This will clean out the existing versions of the frameworks. This isn't strictly necessary, you could just re-install over the top of the old frameworks, but deleting then manually copying over the new ones will clean up any old frameworks that are no longer included in the standard build. 114 114 115 -1. h5. Navigate to the o riginal Wondersourcedirectory thatyou createdaboveduringinitialsource installation115 +1. h5. Navigate to the Roots directory that was automatically created by the initial Source installation procedure above 116 116 117 117 {{code value="none"}} 118 -cd / path/to/WonderSource118 +cd ~/Roots/ 119 119 {{/code}} 120 120 121 -1. h5. Pullthechangesyoudonothaveandmergethemwithyourlocalrepository121 +1. h5. Delete all installed frameworks whose names match the built frameworks in this Roots build folder 122 122 123 123 {{code value="none"}} 124 - gitpull124 +for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done 125 125 {{/code}} 126 126 127 -1. h5. Build theframeworks.127 +1. h5. Navigate to the original Wonder source directory that you created above during initial source installation 128 128 129 129 {{code value="none"}} 130 - antframeworks130 +cd /path/to/WonderSource 131 131 {{/code}} 132 132 133 -1. h5. Navigateto theRootsdirectorythatwasautomatically createdbythe initialSourceinstallationprocedure above133 +1. h5. Pull the changes you do not have and merge them with your local repository 134 134 135 135 {{code value="none"}} 136 - cd ~/Roots/136 +git pull 137 137 {{/code}} 138 138 139 -1. h5. Delete all installed frameworks whose names match the built frameworks in this Roots build folder 140 - 141 -{{code value="none"}} 142 -for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done 143 -{{/code}} 144 - 145 145 {{info}} 146 146 147 147 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.