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=26300>. 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=26300 manifest task munges classpath entries ------- Additional Comments From [EMAIL PROTECTED] 2004-01-22 20:19 ------- I do appreciate the help and effort you're putting in to help resolve this. I'm launching the jar by either a double-click on windows, and java -jar on both platforms. the first error I receive is: naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exeception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory] said class is located in jnp-client.jar. the app launches perfectly when I explode the jar, place the class-path entry on all one line (yes, against the spec), and then repackage. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
