Re: [akka-user] Re: Akka Http 10.1.0 Released

2018-03-09 Thread Konrad Malawski 
Excellent, thanks for reporting back :)

-- 
Konrad Malawski

On March 10, 2018 at 15:52:46, Gavin Baumanis (gavinbauma...@gmail.com)
wrote:

> Congratulations to all!
> Thanks very much for your ongoing efforts!
>
> I have updated our application to the new version and all my tests pass
> and the application is running as expected.
>
>
> Gavin.
>
> On Friday, 9 March 2018 06:04:19 UTC+11, Johannes Rudolph wrote:
>>
>> Dear hakkers,
>>
>>
>> we are happy to announce Akka Http 10.1.0, the first release of the
>> 10.1.x series.
>>
>>
>> See the announcement at https://akka.io/blog/news/
>> 2018/03/08/akka-http-10.1.0-released.
>>
>>
>> The most important changes are:
>>
>>- The new client pool implementation introduced in 10.0.11 is now the
>>default. We have identified and fixed several bugs in the RC period so by
>>now we are quite confident that the new client pool will be a solid
>>replacement for the legacy one.
>>- Documentation has been completely consolidated between Scala and
>>Java pages. Hundreds of directive documentation pages have been merged in 
>> a
>>tireless effort by @jonas , @jlprat
>>, and Akka team’s @raboof
>>. The overall documentation structure has
>>been improved.
>>- Experimental artifacts are available for Scala 2.13.0-M3.
>>- Support for Akka 2.4.x, which is at its end-of-life with the end of
>>2017, has been removed. In the future, this will allow us to make use of
>>features that only Akka 2.5 supports.
>>- Methods deprecated during the life-time of Akka HTTP 10.0.x have
>>been removed. Methods just deprecated for 10.0.11 have not yet been 
>> removed
>>to allow for a smooth transition.
>>
>> New client pool implementation is now the default
>>
>>
>> The new client pool implementation introduced in 10.0.11 is now the
>> default. Since 10.0.11, we fixed several bugs in the new client pool
>> implementation. You can still fall back to the old implementation by
>> setting akka.http.host-connection-pool.pool-implementation = legacy.
>>
>> Akka is not an explicit dependency anymore / Removal of Akka 2.4 support
>>
>> Akka HTTP 10.0.x has always supported Akka 2.5, while allowing users to
>> still remain on Akka 2.4.x if they choose to do so. By now Akka 2.4 has
>> reached its end of life. Therefore, Akka HTTP 10.1.x only supports Akka >=
>> 2.5.11 (and future versions during the life of Akka HTTP 10.1.x) so we will
>> be able to make of features only provided by Akka 2.5. In some cases we
>> bump the minimum supported patch version of Akka to be able to use new
>> features quickly.
>>
>>
>> Using Akka HTTP with Akka 2.5 used to be a bit confusing, because Akka
>> HTTP explicitly depended on Akka 2.4. Trying to use it together with Akka
>> 2.5, running an Akka HTTP application could fail with class loading issues
>> if you forgot to add a dependency to both akka-actor and akka-stream of
>> the same version. For that reason, we changed the policy not to depend on
>> akka-stream explicitly anymore but mark it as a provided dependency in
>> our build. That means that you will always have to add a manual
>> dependency to akka-stream (veterans may remember this policy from Spray).
>>
>>
>> Please make sure you have chosen and added a dependency to akka-stream when
>> updating to the new version.
>>
>>
>> Currently, the right dependency to add is
>>
>>
>> libraryDependencies += "com.typesafe.akka" %% "akka-stream" % "2.5.11"
>>
>>
>> Support for Scala 2.13.0-M3
>>
>>
>> Akka HTTP 10.1.0 is released for Scala 2.11, 2.12, and 2.13.0-M3. Due to
>> a regression in Scala 2.13.0-M3
>>  tail call optimization
>> does not apply anymore in some cases where it did before which might lead
>> to stack overflow when running with Scala 2.13.0-M3.
>>
>> Deprecation Removals
>>
>> Methods were removed that have been deprecated during the life-time of
>> Akka HTTP 10.0.x. Methods that were only deprecated in the last release of
>> Akka HTTP, 10.0.11, are not yet removed to allow for a smooth transition.
>> In general, our guarantee for minor release updates is that code that
>> compiled on the latest version of the previous minor release (10.0.11 in
>> this case) should be both source and binary compatible with the latest
>> version of the current minor release. We might make exceptions to the rule
>> for cases where the maintenance burden seems greater than the risk of
>> breaking major users / third-party libraries. We’ll treat any other binary
>> incompatibilities as regressions.
>>
>> Compatibility Notes
>>
>> As the compatibility notes
>>  
>> explain
>> in detail, we guarantee binary compatibility. In some cases, however, a new
>> version is not strictly source compatible. We try to limit the impact of
>> these kinds of changes but some

[akka-user] Re: Akka Http 10.1.0 Released

2018-03-09 Thread Gavin Baumanis 
Congratulations to all! 
Thanks very much for your ongoing efforts!

I have updated our application to the new version and all my tests pass and 
the application is running as expected.


Gavin.

On Friday, 9 March 2018 06:04:19 UTC+11, Johannes Rudolph wrote:
>
> Dear hakkers,
>
>
> we are happy to announce Akka Http 10.1.0, the first release of the 10.1.x 
> series.
>
>
> See the announcement at 
> https://akka.io/blog/news/2018/03/08/akka-http-10.1.0-released.
>
>
> The most important changes are:
>
>- The new client pool implementation introduced in 10.0.11 is now the 
>default. We have identified and fixed several bugs in the RC period so by 
>now we are quite confident that the new client pool will be a solid 
>replacement for the legacy one.
>- Documentation has been completely consolidated between Scala and 
>Java pages. Hundreds of directive documentation pages have been merged in 
> a 
>tireless effort by @jonas , @jlprat 
>, and Akka team’s @raboof 
>. The overall documentation structure has 
>been improved.
>- Experimental artifacts are available for Scala 2.13.0-M3.
>- Support for Akka 2.4.x, which is at its end-of-life with the end of 
>2017, has been removed. In the future, this will allow us to make use of 
>features that only Akka 2.5 supports.
>- Methods deprecated during the life-time of Akka HTTP 10.0.x have 
>been removed. Methods just deprecated for 10.0.11 have not yet been 
> removed 
>to allow for a smooth transition.
>
> New client pool implementation is now the default
>
>
> The new client pool implementation introduced in 10.0.11 is now the 
> default. Since 10.0.11, we fixed several bugs in the new client pool 
> implementation. You can still fall back to the old implementation by 
> setting akka.http.host-connection-pool.pool-implementation = legacy.
>
> Akka is not an explicit dependency anymore / Removal of Akka 2.4 support
>
> Akka HTTP 10.0.x has always supported Akka 2.5, while allowing users to 
> still remain on Akka 2.4.x if they choose to do so. By now Akka 2.4 has 
> reached its end of life. Therefore, Akka HTTP 10.1.x only supports Akka >= 
> 2.5.11 (and future versions during the life of Akka HTTP 10.1.x) so we will 
> be able to make of features only provided by Akka 2.5. In some cases we 
> bump the minimum supported patch version of Akka to be able to use new 
> features quickly.
>
>
> Using Akka HTTP with Akka 2.5 used to be a bit confusing, because Akka 
> HTTP explicitly depended on Akka 2.4. Trying to use it together with Akka 
> 2.5, running an Akka HTTP application could fail with class loading issues 
> if you forgot to add a dependency to both akka-actor and akka-stream of 
> the same version. For that reason, we changed the policy not to depend on 
> akka-stream explicitly anymore but mark it as a provided dependency in 
> our build. That means that you will always have to add a manual 
> dependency to akka-stream (veterans may remember this policy from Spray).
>
>
> Please make sure you have chosen and added a dependency to akka-stream when 
> updating to the new version.
>
>
> Currently, the right dependency to add is
>
>
> libraryDependencies += "com.typesafe.akka" %% "akka-stream" % "2.5.11"
>
>
> Support for Scala 2.13.0-M3
>
>
> Akka HTTP 10.1.0 is released for Scala 2.11, 2.12, and 2.13.0-M3. Due to a 
> regression 
> in Scala 2.13.0-M3  tail 
> call optimization does not apply anymore in some cases where it did before 
> which might lead to stack overflow when running with Scala 2.13.0-M3.
>
> Deprecation Removals
>
> Methods were removed that have been deprecated during the life-time of 
> Akka HTTP 10.0.x. Methods that were only deprecated in the last release of 
> Akka HTTP, 10.0.11, are not yet removed to allow for a smooth transition. 
> In general, our guarantee for minor release updates is that code that 
> compiled on the latest version of the previous minor release (10.0.11 in 
> this case) should be both source and binary compatible with the latest 
> version of the current minor release. We might make exceptions to the rule 
> for cases where the maintenance burden seems greater than the risk of 
> breaking major users / third-party libraries. We’ll treat any other binary 
> incompatibilities as regressions.
>
> Compatibility Notes
>
> As the compatibility notes 
>  
> explain 
> in detail, we guarantee binary compatibility. In some cases, however, a new 
> version is not strictly source compatible. We try to limit the impact of 
> these kinds of changes but sometimes, they are inevitable to improve the 
> API.
>
> Source incompatible changes are:
>
>- Removed deprecated methods from 10.0.x
>- ServerBinding.unbind return type has been changed to Future[Done] / 
>