Forcing woapp appstart instead of woapp_52 appstart
Forcing woapp appstart instead of woapp_52 appstart
- Subject: Forcing woapp appstart instead of woapp_52 appstart
- From: Gary Teter <email@hidden>
- Date: Tue, 14 Jul 2009 12:19:02 -0700
WOLips 3.4.5744, Eclipse 3.4.2, WebObjects 5.3, Mac OS X Server 10.4.11
I'm trying to get with the times and migrate over from Eclipse 3.3,
and I think I've got everything down except building applications for
deployment. The script generated at Contents/MacOS/<appname> contains
if [ "${HOME}" = "" ]
then
echo ${SCRIPT_NAME}: HOME environment variable is not set!
Terminating.
exit 1
fi
which causes wotaskd to terminate the script instead of launching the
app. As far as I can tell, I should be able to force use of the old-
style script by setting wo.bootstrapjar=/tmp/
forcewoboostrapjartobemissing in my wolips.properties file (or
renaming /System/Library/WebObjects/JavaApplications/wotaskd.woa/
WOBootstrap.jar)... but I still get the new-style script instead.
What am I missing? Thanks for any insights!
--
The Loaf Question: http://wirehose.com/research/entvisualization/
_______________________________________________
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