Skip to content
This repository was archived by the owner on May 25, 2023. It is now read-only.

Conversation

@eed3si9n
Copy link
Contributor

@eed3si9n eed3si9n commented Jan 7, 2019

Ref #104, #103
Ref https://discuss.lightbend.com/t/no-configuration-setting-found-for-key-decode-max-size/2738
Ref lagom/lagom#1652

As per recommendation by Play/Lagom team, I am downgrading the Akka HTTP to 10.0.15, which aligns with Lagom 1.4.x, as opposed to 10.1.5 that's compatible with Lagom 1.5.x.

/cc @lightbend/play-lagom

Ref #104, #103
Ref https://discuss.lightbend.com/t/no-configuration-setting-found-for-key-decode-max-size/2738
Ref lagom/lagom#1652

As per recommendation by Play/Lagom team, I am downgrading the Akka HTTP to 10.0.15, which aligns with Lagom 1.4.x, as opposed to 10.1.5 that's compatible with Lagom 1.5.x.
@eed3si9n eed3si9n requested a review from octonato January 7, 2019 18:34
@ghost ghost assigned eed3si9n Jan 7, 2019
@ghost ghost added the review label Jan 7, 2019
@patriknw
Copy link
Contributor

patriknw commented Jan 7, 2019

That is correct until we release Akka management 0.50 and reactive-lib for that. Then we will have two branches, one for Lagom 1.4 and another for Lagom 1.5

@eed3si9n eed3si9n merged commit 8f26113 into master Jan 8, 2019
@ghost ghost removed the review label Jan 8, 2019
@eed3si9n eed3si9n deleted the wip/akka-http-again branch January 8, 2019 15:44
@eed3si9n eed3si9n added this to the 1.6.0 milestone Jan 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants