On 13/11/2007, at 12:13 PM, Kieran Kelleher wrote:
Lachlan,
AFAIK, if 1.5 is present on the system somewhere, even if not
default (if using OS X Tiger Server with 1.4 as default for
example), then you can specify the path to the java executable in
the MacOSClassPath.txt in the woa and sti
Lachlan,
AFAIK, if 1.5 is present on the system somewhere, even if not default
(if using OS X Tiger Server with 1.4 as default for example), then
you can specify the path to the java executable in the
MacOSClassPath.txt in the woa and still run under 1.5 even if 1.4 is
the default for the
Quick question,
On 13/11/2007, at 4:14 AM, Mike Schrag wrote:
Lots of people have been plagued with classpath oddities
(especially the Session and the Main class one matching javamail
and log4j respectively). After much digging, the "official
unofficial" causes seem to be:
1) When launc
Am 12.11.2007 um 18:14 schrieb Mike Schrag:
1) When launching from Eclipse, bundle loading works a little
differently, and I believe Anjo's fixes to WOLips should have this
resolved now.
Be aware that the current fix reorders the debug or runtime classpath
to move App and Project jars/cl
Lots of people have been plagued with classpath oddities (especially
the Session and the Main class one matching javamail and log4j
respectively). After much digging, the "official unofficial" causes
seem to be:
1) When launching from Eclipse, bundle loading works a little
differently, a
