Re: Frameworks and versioning
Re: Frameworks and versioning
- Subject: Re: Frameworks and versioning
- From: Anjo Krank <email@hidden>
- Date: Thu, 5 Jan 2006 22:40:06 +0100
Am 05.01.2006 um 21:58 schrieb Chuck Hill:
but there's no obvious way to link to a specific deployed version
of a framework (at least, within Xcode) within a WebObjects
Application as there is for a Cocoa app. The thing that this would
enable is either being able to deploy/depend on certain
compatibility version and/or testing a new version of a framework
(e.g., version "C" with a test app) prior to changing the Current
symlink to point to "C" for other apps to benefit (if applicable).
AFAIK, this is not handled. It would have to be encoded into the
classpath files (MacOSClassPath.txt etc.) and then handled by
WOBootStrap when it generates the Java command line (with
classpath). I've never seen any indication that this was
implemented. I don't know if the WOBootStrap source is available,
I don't think so. There is an Open Source alternative (http://
www.objectstyle.org/woproject/articles/WOFLobotomy1/) that could be
extended to handle this, but Xcode still won't put the necessary
info in the classpath files.
Did you try the argument
-DWOLocalRootDirectory="/Network/Libs/Release37"
in your launch args? Where /Network/Libs/Release37 is what / is on
the Mac or $NEXT_ROOT/Local on Solaris....
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden