CARVIEW |
Navigation Menu
-
Notifications
You must be signed in to change notification settings - Fork 349
tomcat8 support #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tomcat8 support #28
Conversation
Hello, My name is Cyrille Le Clerc, I am in charge of the Tomcat 8 support on CloudBees platform and I am interested in contributing to this enhancement. I see many changes in the testing framework the following classes must be changed to use the Tomcat 8's org.apache.catalina.startup.Tomcat instead of Tomcat 7's org.apache.catalina.startup.Embedded:
My unit tests still don't pass but I can contribute it to this pull request whenever someone is interested. |
do you want to copy the tomcat 7 tests or is your code based on one general tool that encapsulates the functionality of Embedded and Tomcat classes? |
First of all thanx a lot @h0nIg for the initial pull request! I appreciate this a lot even if I didn't take time to take further steps towards tomcat8 support. Now that there are RCs available (via maven) it's easier to work on this. @cyrille-leclerc I'd be happy if you'd contribute to this pull request! The tests use(d) I think with the support for tomcat8 we can cancel tomcat6 support (split off a tomcat6 branch to be able to backport fixes if this would be needed) and move tests from @h0nIg @cyrille-leclerc WDYT? |
Hi,
|
IMHO we can continue to work on 'tomcat8' - assuming that your work is based on @h0nIg. Still, if you think it would make more sense to work on a v2 just go ahead.
Absolutely. I'm under very high pressure due to a preso at the end of next week, so I won't have time before in 2 weeks either (sorry for my bad english ;-)). |
"Embedded vs. Tomcat and end of support for Tomcat6" i dont think it is a very good idea to "drop" the support for tomcat 6, since tomcat will get maintenance updates as long as tomcat 9 will be released. (https://www.tomcatexpert.com/blog/2013/01/31/java-6-end-life-impact-apache-tomcat-users) "Since the community supports 3 versions at any time, Tomcat 6 will continue to be supported until Tomcat 9 becomes active, so we should expect at least another two to three years of active support and development on Tomcat 6." @cyrille-leclerc do you think a solution is possible that will address all active tomcat versions? or do you think that a solution with an interface/implementation per version of Tomcat and Embedded that will do the necessary work for the tests is a very bad idea/not possible? |
Thanx for this information @h0nIg! Then maybe we should keep support for tomcat 6. According to the google code downloads the tomcat6 jar makes still ~35% of both tc7+tc6 downloads, and the sonatype statistics show the same ratio. So it would be great if we could introduce an additional interface and implementations for Embedded and Tomcat. |
Changes between tc7 and tc8: Package changed
Disappeared
Problems
|
Hi, I may have made a mistake with github. I created #30 . One test is unfortunately still failing, see pull request 30 for details. |
Thanx @h0nIg (Hans-Joachim Kliemeck) and @cyrille-leclerc (Cyrille Le Clerc). See also pull requests #28 and #30 Tomcat8 now redirects with 303 instead of 302. For 303 httpclient automatically redirects, so httpclient must be asked not to do so, additionally the status code checks in TestUtils needed to be extended for 303. Change context path to "" to get rid of tomcat8 //login workaround
No description provided.