Stefan,
I'll remove the classpath element of the manifest. it is historic and not used anymore (to my knowledge).
I don't know the ancestory of the javax classes in geronimo. I would assume
they came from jakarta, but I don't know for sure. At the time I switched I did so as the geronimo classes had been updated with the apache 2 license.
cheers
Stefan Bodewig wrote:
Thanks for the quick help, Greg.
On Wed, 20 Oct 2004, Greg Wilkins <[EMAIL PROTECTED]> wrote:
But I'm curious as to why you are getting this problem? The servlet classes should not be in the org.mortbay.jetty.jar file.
They are not.
They should only be in javax.servlet.jar.
Which gets pulled in by org.mortbay.jetty.jar via the Class-Path attribute in the MANIFEST.MF.
If you have multiple sources of the servlet API, then perhaps it would be best to somehow only include one of them.
Absolutely, and that's what Gump wants to do. It gets defeated by the Class-Path attribute and the sealing adds another layer to the problem.
Thinking about it a second time, not sealing will probably only help those Gump builds that want the same version of javax.servlet that Jetty provides, all others may still be in trouble.
The Jetty servlet API files are taken directly from the apache geronimo project.
Dumb question, are they different from those inside the jakarta-servletapi(-4|5) CVS modules at Apache?
Cheers
Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
