NEXT_ROOT + embedding + unix/Linux
NEXT_ROOT + embedding + unix/Linux
- Subject: NEXT_ROOT + embedding + unix/Linux
- From: Gavin Eadie <email@hidden>
- Date: Mon, 25 Jun 2012 12:56:33 -0400
If you build an application with all its frameworks embedded, the
environment variable NEXT_ROOT is never used. If you then deploy this
app on a non-Windows/non-MacOSX system, the launch script
"xxx.woa/xxx" will terminate because NEXT_ROOT is not defined, and the
app will not launch. I suspect that embedding and linux deploys are
becoming more common so, while this might have been an unusual
circumstance years ago, it isn't unusual today.
It is, of course, easy to define the variable and dodge this issue,
but I find myself in a situation where this is less desirable. I'm
sending out an 'all-frameworks-embedded' app to a few people to run in
direct connect mode and one-by-one they've tripped over
NEXT_ROOT environment variable is not set! Terminating.
I could fix this by dropping an export NEXT_ROOT="" into the top of
the launch script, but I don't like changing standard files (somebody
downstream will get confused). I could change the WOLips build.xml
file or (gasp) the <woapplication> ant task but that's even less
attractive.
The mail list archive don't have any discussion of this, and I'm
wondering if this is something that has been resolved in a way that is
widely accepted by this community as the "right way"?
_______________________________________________
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