On 11/09/2007, at 1:27 PM, Mike Schrag wrote:
This is our plan as well ... In development, I actually have both
sets of frameworks on Tiger, and I just run a script to swap
between the two if I want to test. In deployment, I plan on
embeddeing 5.3 until we're ready/willing/able to use 5.4.
I suppose what I was thinking about was: would it be practical/
possible to set up alternate NEXT_ROOTs such as NEXT_ROOT_54,
NEXT_ROOT_53?
i.e., the classpath files generated for an app include the path to
these libraries utilising NEXT_ROOT etc, so perhaps the tools (such
as WOLips) could perhaps provide a way of adjusting these paths for a
given deployment environment by being able to adjust the name of the
env variable used when building the classpath files.
Otherwise, embedding it is...
Thanks.
On Sep 10, 2007, at 10:56 PM, David LeBer wrote:
On 10-Sep-07, at 10:46 PM, Lachlan Deck wrote:
seeing as WO 5.4 is seemingly just 'round the corner, and it
*may* break things I was wondering if anyone has thought through
(or is already) setting up WO frameworks so that differing
versions can co-exist on the same machine.
i.e., setting up multiple NEXT_ROOTs?
Embedding the entire framework tree in each application is of
course an option, but a hefty one that would be nice to avoid.
This is what we are doing. The apps are a bit big (OK, a lot big)
but it certainly wins on the "easy" meter.
Any thoughts?
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
