Struts 1.x then remains Servlet 2.2, JSP 1.1, Java 1.2.
Struts 2.x (fka 1.3.x) can then be Servlet 2.3, JSP 1.2, and Java 1.3.
Struts 3.x (fka 2.x) can then be Servlet 2.4 and JSP 2.0, as planned.
If we are going to depend on Servlet 2.3, then I think it's probably worth changing the major version number.
So why not just label want we were going to do in 1.3.x as Struts 2.x, and start calling Jericho (or whatever else we do -- it's just a whiteboard) 3.x ?
However, I don't know if I believe it's worth the potential confusion and management overhead to switch to 2.3 "just because". I do think it's true that Struts can set an example and help people become familiar with new technologies, but why not do Struts 1.3 as we've planned it, unless someone has specific features they want to apply that we require?
In summary, I'd say "stay the course" until there's a specific proposal to use Servlet 2.3 features , but if we start using 2.3 features, we should bump the major version. But it seems to me that any interesting use of Servlet 2.3 is probably going to involve other sizeable refactorings that would also justify incrementing the major version number.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
