In the new nightly, you can do combinations of:
1) Prefs=>WOLips=>Build and set the WOLips Properties file (workspace
default)
2) in your project build.properties, set wolips.properties=xxx
3) in your project build.properties, override any values from
wolips.properties
For #1 and #2, if you specify a filename (with no path) it will load
Library/Application Support/WOLips/thatfile as your
wolips.properties. This is recommended for team environments.
Alternatively you can set a full path and it will use that instead.
This allows you to specify wolips.wo53.properties,
wolips.wo54.properties, etc and select them per-project.
Note that if you're using Source projects for Project Wonder (or other
dependent frameworks) and using method #2, this will present some
issues because your framework will be built potentially one way
independent of your app. The recommended method, in my opinion, is to
make a 5.3 workspace and a 5.4 workspace and use method #1 and set a
workspace global setting. This will keep your projects isolated and
building properly including all source project dependencies (you could
have Wonder checked out in both and it would build in 5.4 in one and
5.3 in the other).
This should make it easier for people to try out new versions of
WebObjects when they come out. Obviously if you're using Maven, you
don't really have this issue as you're already building against the
correct version jars by default .... of course you had to exchange
your soul for this feature, but I'm not judging ;)
ms
This archive was generated by hypermail 2.0.0 : Mon Jan 19 2009 - 19:21:43 EST