-
Notifications
You must be signed in to change notification settings - Fork 44
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
Base ssl-proxies-tomcat on tomcat7 #28
Comments
Hi, Tomcat6 is in maven in fact: <dependency>
<groupId>org.apache.tomcat</groupId>
<artifactId>catalina</artifactId>
<version>6.0.24</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.tomcat</groupId>
<artifactId>coyote</artifactId>
<version>6.0.24</version>
<scope>provided</scope>
</dependency> Best, |
For me, whether it is in the maven repo or not is not important. I never claimed it wasn't (that was Brian). I think it is a good thing to do for other reasons. This is more about keeping the dependencies updated, similar to when bc 1.46 was replaced with bc 1.49 as the bouncycastle dependency. You can still build for tomcat 5, 6 and 7 just as before. This patch only changes which is selected by default if no profile is requested. Fedora no longer provides tomcat 6 since Fedora 19. |
I'm happy with making tomcat7 the default. @jrevillard - any objections? |
Absolutely no objection as far as I can still produce tomcat6 version... which is the case. Best. |
Why is this still open? |
Right now, the ssl-proxies-tomcat code is based on tomcat6. Tomcat6 isn't in maven, meaning things don't compile in the default profile.
The text was updated successfully, but these errors were encountered: