On Fri, Jun 07, 2013 at 02:14:59PM -0400, Mark H. Wood wrote:
Java EE 7 is released. Tomcat 8 will therefor be coming along
sometime soon. Meaning that Tomcat 5.5 will reach EOL soon.
I understand that voting on Tomcat 8 RC1 has commenced.
--
Mark H. Wood, Lead System Programmer
Our instances are on boxes that have been running as-is since 2008, thus
Tomcat 5.5. I'm fine with the future DSpace release to migrate to the next
standard servlet version.
We're in the process of infrastructure migration, so us moving to the
latest tomcat would be our plan too.
So, +1 with
Further to this, I think that Tomcat x.y is really just an example
of what we really depend on: servlet-api x.y and jsp-api x.y.
Probably we should document it that way, giving examples of Tomcat,
Jetty, and Resin versions which meet the API requirements.
--
Mark H. Wood, Lead System Programmer
On Mon, Jun 10, 2013 at 2:57 PM, Mark H. Wood mw...@iupui.edu wrote:
Further to this, I think that Tomcat x.y is really just an example
of what we really depend on: servlet-api x.y and jsp-api x.y.
Probably we should document it that way, giving examples of Tomcat,
Jetty, and Resin versions
Java EE 7 is released. Tomcat 8 will therefor be coming along
sometime soon. Meaning that Tomcat 5.5 will reach EOL soon.* And (my
ulterior motive) I need a ServletContext method that was introduced in
servlet-api 2.5, while Tomcat 5.5 provides servlet-api 2.4.
My selfish wishes aside, is it
Yes, I think it's logical to require Tomcat 6 or above in DSpace 4, for
all the reasons you mention. I doubt there are many users on Tomcat 5.5
anymore (most OS package managers have Tomcat 6 or 7). Even if they did,
we can recommend a Tomcat upgrade alongside their next DSpace upgrade.
- Tim
