The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Sat, 17 Apr 2004 8:09 AM
Changes:
assignee changed from Cactus Developers Mailing List to Vincent Massol
description changed from 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. to 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.
environment changed from Operating System: MacOS X
Platform: Macintosh to Operating System: MacOS X
Platform: Macintosh
priority changed to Blocker
Fix Version changed to 1.6
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-82?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-82
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-82
Summary: containers fail looking for tools.jar on Mac OS X
Type: Bug
Status: Resolved
Priority: Blocker
Resolution: FIXED
Project: Cactus
Components:
Ant Integration
Fix Fors:
1.6
Assignee: Vincent Massol
Reporter: Joe Germuska
Created: Sun, 7 Dec 2003 4:51 AM
Updated: Sat, 17 Apr 2004 8:09 AM
Environment: Operating System: MacOS X
Platform: Macintosh
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
