Apache does indeed have Apache-licensed versions of the servet 2.4 (and JSP 2.0) API classes. The ones that are shipped with Tomcat 5.x are in cvs repository "jakarta-servletapi-5". I would imagine we could just get the Tomcat folks to post those JARs to ibiblio or something. Isn't that just a matter of uploading to some special directory on an Apache server that gets mirrored over (the same way we do the Struts JARs)?
This is exactly what should happen; i just didn't want to join the tomcat mailing list just to try to get it started!
I also wouldn't really feel comfortable building the JAR myself. But all that really needs to happen is for someone to place the the final version on cvs.apache.org in "/www/www.apache.org/dist/java-repository/servletapi/jars" -- the mirroring process will take care of the rest.
The Maven convention is to use the same name for the "group ID" (the part that comes before "jars" in the path) and the "artifactID" (the part that is the name of the JAR, except for the version number), although when necessary, those can diverge. So I guess I was expecting to see:
/www/www.apache.org/dist/java-repository/servletapi/jars/servletapi-2.4.jar
We could certainly have struts-shale depend on servlet-api-2.4-20040521.jar, which seems reasonably current. But since that postdates the official release date, maybe we want to be more clear about what we're depending on. I wonder who put that one up (which appears to have been put up via the Apache mirroring process) and why it has a timestamp instead of a full release version?
I know that the maven build is just one alternative, so I don't want to make this a big to-do.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana
