-
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
Cut a release for Guice 4.0.0 final #45
Comments
I can't believe they finally did it. I should look at this Monday as I am out of town. |
I've updated the snapshot version 4.0.0-SNAPSHOT. Give that a spin and if the wheels don't fall off let me know and I'll promote it to 4.0.0 |
I tried using snapshot but sbt could not resolve it. Do I have to add a new Thanks. On Tue, May 12, 2015 at 9:30 AM, Thomas Suckow [email protected]
|
Well this is embarrassing. All this time I thought I was pushing SNAPSHOT releases I had a typo. It should "just work" now. But if not it is at https://oss.sonatype.org/content/repositories/snapshots/ Or if you wanted to download the jar directly for some reason oss.sonatype.org/.../scala-guice_2.11/4.0.0-SNAPSHOT/ |
Ok, after I added resolvers += Resolver.sonatypeRepo("snapshots"), all my Thanks. On Tue, May 12, 2015 at 11:17 AM, Thomas Suckow [email protected]
|
Just tested the 4.0.0-SNAPSHOT in our project and everything works as expected. And as a bonus the Guava evicted messages (#40) will finally be fixed \o/. |
Good to hear! I am trying to get #44 squared away. I am swamped, I hope to make a new snapshot tonight changing the related dependency and then hopefully get the full release out before the long weekend. |
I was almost done with #42 well back in the day. Does it make sense to finish that off? An almost complete implementation is here: https://github.com/nbauernfeind/scala-guice/tree/TypeTag. However, I think we would need to drop support for scala 2.10 since TypeTag's are not thread safe (see: http://docs.scala-lang.org/overviews/reflection/thread-safety.html). 2.11 has been release for only about a year (since 4/16/2014). Or, if not dropping support, we could branch off of 2.10 but some changes would not be portable. Maybe we could have one last 2.10 release to celebrate Guice's 4.0? |
I am thinking we could keep support for 4.0.0 and then drop support and do
a 4.0.1. If too much protest we keep a branch for 2.10 after that.
|
Should be synced to maven central shortly |
Cool, thanks. On Tue, May 26, 2015 at 7:36 AM, Thomas Suckow [email protected]
|
No description provided.
The text was updated successfully, but these errors were encountered: