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-06 09:51 ------- 1) Take the good habit to have nothing in lib/ext. lib/ext is evil. As long as you will have something here you are shooting yourself in the foot. 2) It's no magic, it means that you have at least one jar in your classpath that has sealed:true in its manifest. For instance that's the case of JAXB (and the rt has SAX and DOM interfaces here so you can be sure that it won't work) 3) It's not an OS issue and it's not an Ant issue. More globally it's a Java issue because of a prehistoric thing called 'classpath', a missing lib versioning in Java and a complete lack of coherence in creating jars. It is a nonsense to create a jar with its dependencies stuffed into it because then you will be stuck when you will have one jar that is stuffed w/ v1.0 and another one that is stuffed w/ v1.2 4) Do a dump of all your System.properties to look at what jar are included when running your vm. 5) As it is not an Ant issue, this bug should be closed. If you need help for such settings then I highly recommend to post in [email protected], bugzilla is for bug report not for discussions. Hope this helps. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
