On Feb 25, 2008, at 10:18 AM, Johan Henselmans wrote:
The problem appears in the MacOSClasspath.txt and the
MacOSXServerClasspath.txt. Inside was the line with ${jvm} instead
of java. I discovered that the line was important after I rebooted
in 10.4.x, got a whole slew of updates, rebooted, downloaded the
last WOLips and then happened to get exactly the same error if I
constructed a WonderD2W application. A normal Wonder App would not
have this ${jvm} but a plain java on the first line. Replacing if
with java solved the problem. I don't know where this comes from,
or how this is constructed.
It looks suspiciously like a an unset Ant property.
I must say it is one of the most bizarre errors I have found : a
commented line that causes trouble. Make me remind of the version
of bind where tabs have to be tabs and spaces had to be spaces and
good luck to you all...
It is actually NOT a commented line. In these files, it indicates
lines that are not paths for the classpath, but some other values
that the startup jar needs. It was a uniquely poor choice of
character to indicate this!
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
