Last modified by D Tim Cummings on 2022/07/27 02:24

From version 66.1
edited by pgr
on 2010/02/18 22:07
Change comment: There is no comment for this version
To version 67.1
edited by David Avendasora
on 2011/06/13 01:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pgr
1 +XWiki.avendasora
Content
... ... @@ -1,4 +1,4 @@
1 -The following are instructions on how to setup Eclipse / WOLips so you can work with mulitple versions of WebObjects. This tutorial will demonstrate setting up your environment simply for WebObjects 5.3.3 and 5.4.3 but there's no reason you can't have different setups based on customer or project instead.
1 +The following are instructions on how to setup Eclipse / WOLips so you can work with mulitple versions of WebObjects. This tutorial will demonstrate setting up your environment simply for WebObjects 5.3.3 and 5.4.3 but there's no reason you can't have different setups based on customer or project instead.
2 2  
3 3  ==== Create New Directory Structure ====
4 4  
... ... @@ -12,7 +12,7 @@
12 12  
13 13  [[image:http://wiki.objectstyle.org/confluence/download/attachments/5275708/media_1245677004032.png?version=10||align="centre"]]
14 14  
15 -We now need to download the ##WOInstaller.jar## file from ##http:~/~/webobjects.mdimension.com/wolips/## and save it into the ##Versions/## directory we just created.
15 +We now need to download the ##WOInstaller.jar## file from ##[[http://webobjects.mdimension.com/wolips/]]## and save it into the ##Versions/## directory we just created.
16 16  
17 17  ==== Use WOInstaller.jar to download WebObjects ====
18 18  
... ... @@ -39,7 +39,7 @@
39 39  
40 40  [[image:http://wiki.objectstyle.org/confluence/download/attachments/5275708/media_1245679819648.png?version=10||align="centre"]]
41 41  
42 -You need to launch Eclipse and WOLips at least once so that it will create the default ##wolips.properties## file in ##,,/Library/Application Support/WOLips/,,##,,. If you've already been using WOlips, you can skip this step.,,
42 +You need to launch Eclipse and WOLips at least once so that it will create the default ##wolips.properties## file in ##/Library/Application Support/WOLips/##. If you've already been using WOlips, you can skip this step.
43 43  
44 44  {{note title="Note"}}
45 45  
... ... @@ -103,13 +103,13 @@
103 103  {{note title="Note"}}
104 104  
105 105  This setting currently affects only the Eclipse _internal_ builder - it will not influence external builds with Ant. That is, when you build your project (e.g. for deployment) using any of the following:
106 -- Ctrl-click {{build.xml}} -> Run As -> Ant Build
107 -- WOLips Ant Tools -> Install
106 +- Ctrl-click {{build.xml}} \-> Run As \-> Ant Build
107 +- WOLips Ant Tools \-> Install
108 108  - build with Ant from the command line
109 109  
110 110  ...this setting will not affect where Ant looks for the various resources specified by the settings in your alternate {{wolips.properties}}.
111 111  
112 -In order to configure Ant so that it can find your {{wolips.properties}}-specified resources, you'll need to use Option 2, below.
112 +In order to configure Ant so that it can find your {{wolips.properties}}\-specified resources, you'll need to use Option 2, below.
113 113  
114 114  {{/note}}
115 115  
... ... @@ -117,7 +117,7 @@
117 117  
118 118  [[image:build.properties.png||align="centre"]]
119 119  
120 -Currently, the Eclipse Ant builder is not controlled by the "WOLips -> Build" setting in Eclipse's Preferences. In order to build with Ant, you first need to tell Ant where to find your WebObjects installation and other resources. Your project's default Ant buildfile, ##build.xml## (which is created by WOLips when you create a new WebObjects application project), reads and uses the properties found in your ##$HOME/Library/Application Support/WOLips/wolips.properties## file. But you can specify a different ##wolips.properties## file by adding a line like the following to your project's ##build.properties## file:
120 +Currently, the Eclipse Ant builder is not controlled by the "WOLips > Build" setting in Eclipse's Preferences. In order to build with Ant, you first need to tell Ant where to find your WebObjects installation and other resources. Your project's default Ant buildfile, ##build.xml## (which is created by WOLips when you create a new WebObjects application project), reads and uses the properties found in your ##$HOME/Library/Application Support/WOLips/wolips.properties## file. But you can specify a different ##wolips.properties## file by adding a line like the following to your project's ##build.properties## file:
121 121  
122 122  {{noformat}}
123 123  
... ... @@ -143,7 +143,7 @@
143 143  
144 144  ===== (1) The location of the WOLips ##woproject.jar## file: =====
145 145  
146 -You can do this either via the ##-lib## parameter to the ##ant## command, e.g.
146 +You can do this either via the ##lib## parameter to the ##ant## command, e.g.
147 147  
148 148  {{noformat}}
149 149  
... ... @@ -162,7 +162,7 @@
162 162  
163 163  ===== (2) The location of your ##wolips.properties## file: =====
164 164  
165 -If you already specified this in your ##build.properties## (as per Option 2, above), then you're done. But perhaps you have no interest in building with Ant from within Eclipse, but only want to be able to do Ant builds from the command line. If that's the case, then you can use Ant's ##-D<property>=<value>## command line option to set the value of the ##wolips.properties## Ant property to be the path to your ##wolips.properties## file. Ant will read and process the file specified by the ##wolips.properties## property during the course of processing your ##build.xml##. Again, this path specification can be absolute or relative; but if it's relative, Ant will interpret it as being relative to your project's base folder.
165 +If you already specified this in your ##build.properties## (as per Option 2, above), then you're done. But perhaps you have no interest in building with Ant from within Eclipse, but only want to be able to do Ant builds from the command line. If that's the case, then you can use Ant's ##D<property>=<value>## command line option to set the value of the ##wolips.properties## Ant property to be the path to your ##wolips.properties## file. Ant will read and process the file specified by the ##wolips.properties## property during the course of processing your ##build.xml##. Again, this path specification can be absolute or relative; but if it's relative, Ant will interpret it as being relative to your project's base folder.
166 166  
167 167  Example:
168 168  
... ... @@ -170,10 +170,4 @@
170 170  $ ant -Dwolips.properties=/Users/bubba/Library/Application\ Support/WOLips/wolips.533.properties clean build
171 171  {{/noformat}}
172 172  
173 -As above, you cannot use a tilde character as an abbreviation for your home directory (but you in fact //could// use an environment variable such as ##$HOME## - the shell would expand it before passing it to ant).
174 -
175 -==== OPTIONAL - Building your project using Hudson ====
176 -
177 -{{tip title="Shameless Plug"}}
178 -Come to [WOWODC-East|http://www.wocommunity.org/wowodc09/east/index.html] for hands-on labs demonstrating how to integrate multiple WebObjects installations with Hudson.
179 -{{/tip}}
173 +As above, you cannot use a tilde character as an abbreviation for your home directory (but you in fact //could// use an environment variable such as ##$HOME## the shell would expand it before passing it to ant).