Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Operating System: MacOS X
Platform: Macintosh
-
25266
Description
If I understand correctly, Cactus doesn't work on OS X because the various container classes try to
find "tools.jar" and add it to the classpath, but OS X doesn't have a separate tools.jar (see mailing
list archives URL.)
The attached tarball has a patch that uses Apple's "preferred" mechanism to determine if the JVM is
running on Mac OS X, and if it is, it skips the attempt to add tools.jar to the classpath (because
Apple includes those classes in the core java classes.jar file)
The patches pass all the Ant tests, but I'm not entirely sure that it solves the problem – I'm pretty
new to Cactus. Still I submit the patches in hopes that someone who knows Cactus better might be
able to confirm the fix while I try to find my way around a bit.
In any case, I didn't find a posted bug about this in Bugzilla, and whether or not my patches fix it,
this is something that should be marked in Bugzilla as needing a fix.