-
Notifications
You must be signed in to change notification settings - Fork 92
Use HTTP sbt repos for JDK6 #247
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
Conversation
cool! I guess if we've separately built/tested on JDK 6, then there's no downside to actually publishing from JDK 8...? |
I don't know how publishing works. If it's HTTPS, it may be trouble. |
eh? I'm saying we should publish from JDK 8 |
Sorry, I hadn't seen your comment. I was just adding an additional comment on this PR, so it wasn't a response to your comment. I don't understand your JDK8 comment, but maybe discuss further on scala/sbt-scala-module#41? |
okay |
Thanks, Seth! |
Workaround the lack of TLS 1.2 support in JDK6 by using http to talk to maven central, as done in scala/scala-xml#247. See scala/sbt-scala-module#41. Fixes scala#169.
Workaround the lack of TLS 1.2 support in JDK6 by using http to talk to maven central, as done in scala/scala-xml#247. See scala/sbt-scala-module#41. Fixes scala#169.
This change has introduced a security vulnerability into this library. |
good point. let's discuss at scala/sbt-scala-module#41 rather than here, since multiple Scala modules are affected |
After #246, the build is broken for JDK6. This workaround fixes it by hard-coding HTTP repos for sbt.
This might be an alternative to upgrading to JDK7, see #237.
More information at scala/sbt-scala-module#41