I forgot to mention on this list my..VM_OPTIONS@ fix. Here's the checkin
comment:
>Fixed new WOApplication jvmOptions support. If your WOApplication task
>doesn't explicitly include a "jvmOptions" attribute, then the jvmOptions
>instance variable was left as its default null value, which would result
>in the..VM_OPTIONS@ template being left in the
>[MacOS|MacOSServer|UNIX]ClassPath.txt files, causing .woa startup to fail
>with the error "Exception in thread "main" java.lang.NoClassDefFoundError:
..VM_OPTIONS@". Fixed by setting default value to an empty string.
Ulrich Köster, ulric..bjectstyle.org, wrote:
>to fix the launching and build bugs introduced with 1.0.5 we should
>release 1.0.6 of woproject/WOLips this evening. Anything speaking
>against this?
I'm game!
.......................................................
Jonathan 'Wolf' Rentzsch http://rentzsch.com
Red Shed Software http://redshed.net (847) 584-7465
PGP: b2af 1a09 f881 ebde c9d6 c4d2 c04f a3c0 3ec5 d5f2
"better" necessarily means "different"
This archive was generated by hypermail 2.0.0 : Thu Aug 07 2003 - 10:23:11 EDT