-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
update Typesafe config to 1.3.0-M3 #17071
Comments
+1 for that.and maybe the cachedConfig is no longer needed |
then it should be1.3.0-M2 :P |
@patriknw This should be done soon as well. |
Requires minor changes in code on our side, I'll solve it |
Great, later we might want to try to remove the caching workaround. Havoc said that the new version might be fast enough. Please create a new ticket for that task. |
I checked if we need
|
Should I create the ticket anyway, to revisit at some point in the future? |
awesome, if you have already checked we don't need a ticket |
=act #17071 Update typesafe-config to 1.3.0
=act akka#17071 Update typesafe-config to 1.3.0
from Havoc:
Here's what's new:
https://github.com/typesafehub/config/blob/master/NEWS.md#130-m1-march-6-2015
It probably makes sense to move current dev versions of akka and play
to this release and see if anything explodes. I would do a 1.3.0 final
before your projects go final, of course.
At this time all the open issues are feature requests or I couldn't
reproduce them. I don't know of anything that's broken. So if you find
anything let me know.
I think akka was implementing the
Config
interface, which has newmethods added, so it probably will not compile.
Config
is "sealed bydocumentation" by the way since Java doesn't have sealed. :-)
However, the optimizations to path parsing in this release may mean
the caching you were doing isn't needed anymore. Details of those
optimizations are at lightbend/config#205
in case you feel like deleting code. I think even more optimization
could be possible but it's already fast so you will have to tell me if
it matters to you.
The text was updated successfully, but these errors were encountered: