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 kicking out old tomcat dependencies.
Peter Dietz
On Fri, Aug 2, 2013 at 3:01 PM, Mark H. Wood <mw...@iupui.edu> wrote:
> 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 mw...@iupui.edu
> Machines should not be friendly. Machines should be obedient.
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Dspace-devel mailing list
> Dspace-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
>
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
