DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5302>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5302 Sealing Violation ------- Additional Comments From [EMAIL PROTECTED] 2001-12-11 11:12 ------- Joe, What are your expectations for ant to do in this situation? Clearly this problem is caused by a mismatch between the classpath context that ant needs and the one you are supplying. What do you expect Ant to do about it? Catch the exception, enum every jar in the classpath and modify their manifests to be unsealed *while they are in use*? Or modifying everyon's JVM to ignore the sealed option? I dont see what can be done here other than adding something to an installation troubleshooting page. Also, given this is a JAXB issue, why not provide some feedback through their channels. Why they didnt provide an ant task in the first place, rather than some solaris shell script as an example I dont know, but it they had they would have found this problem. -steve [sealed is just plain trouble. especially when people seal anything with JAXP in it, those interfaces crop up everywhere; I dont know what they were thinking. You dont need to unzip, edit and rezip though; jEdit lets you edit the manifest in-situ] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
