On my development box I'm currently using Tomcat 8.0 with 5x and 6. We're still on 7.0 in production (5x) but I want to move to 8 when I can find the time.
The only issue I can recall is that Tomcat 8's classloader setup is much more finicky, and that collides with the way I like to deploy webapp.s. I inject a ready-made database connection pool via JNDI, and if I'm not careful to delete the database driver JAR from each DSpace webapp. then 8 will complain that it can't find the driver (because there's one in Tomcat's own classloader, which supplies the pool, and another in the webapp's classloader, and they aren't the same 'Class'es even though they are loaded from identical files). I reckon that most sites won't have that problem. When I have some time, I mean to create an option to leave the database driver JAR out of the webapps during assembly. -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
