Ray,
suggestion: embed="true" for all frameworks solved much of this multi-
version garbage in deployment in the past ... probably easiest route
since WOLips ant tasks have easy "embed" flags
catcall/insult: switch to Eclipse you scardey cat! :-p
jibe: cannot believe you still use XCode :)
compliment: thanks for your email
Cheers, Kieran
On Oct 30, 2007, at 12:30 PM, Ray Kiddy wrote:
1) WO 5.3 is not and will not be supported on Leopard.
2) WO 5.3 works with Java 1.4, which is on Leopard, and so the WO
5.3 runtime should work on Leopard.
3) It has been possible, for quite a while, to have more than one
version of WO on a machine, but Apple will never support this.
Essentially, the theoretical cost of supporting configuration goes
up exponentially, not linearly, with the number of versions on a
system. There will never be a reason for Apple to take on the job
of supporting a machine that has two different versions of WO. But....
Having no tool support, it should be a lot easier to configure
runtimes for multiple versions. Things like soft-linked directory
branches work a lot better when they do not have to deal with the
ObjC bridge and all its associated noise. Project Wonder, for
instance, could include scripts for configuring this. A script
could even check the integrity of deployment installs. While at
Apple, I wrote a "verify your versions" direct action. Too support-
ish and not enough aqua, so not shippable.
I am sure I will come up with other ideas, some even more useless
than some of these, when I actually have a Leopard system. We'll
see. I am open to suggestions, question, jibes, innuendoes,
catcalls, or anything short of insults. No, insults are ok, too. :-)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
