Update dependency com.lightbend.lagom:lagom-javadsl-testkit_2.11 to v1.5.5 - abandoned #599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.4.0
->1.5.5
By merging this PR, the below issues will be automatically resolved and closed:
Release Notes
lagom/lagom
v1.5.5
Compare Source
We are pleased to announce the release of Lagom Framework 1.5.5. This is the latest stable release of Play 1.5.x series.
Changelog
This release mainly includes security and overall fixes.
For more details see the full list of changes.
Credits
Thanks to the community for their detailed bug reports and contributions. Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Dale Wijnand, Ignasi Marimon-Clos, Tim Moore, Sergey Morgunov, Stephan Emmerich, Enno Runne, Marcos Pereira.
Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.
v1.5.4
Compare Source
The Lagom team has released the versions 1.5.4. For a list of the specific changes in Lagom 1.5.4, see the change log.
Highlights
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release: Ignasi Marimon-Clos, Tim Moore, Matthias Kurz, Renato Cavalcanti.
v1.5.3
Compare Source
The Lagom team has released the versions 1.5.3 (due to an error during the release we had to skip 1.5.2). For a list of the specific changes in Lagom 1.5.3, see the change log.
Highlights
++
/+
) Lagom appsCredits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Dale Wijnand, Ignasi Marimon-Clos, Marcos Pereira, Sergey Morgunov, Tim Moore, fgonzalez, Dmitriy Grigoryev.
v1.5.1
Compare Source
These releases bring into Lagom a new
Service Locator
implementation, based on Akka's Service Discovery. This component was previously released as an apart library, lagom-akka-discovery-service-locator, and intended to be a replacement for the Service Locator previously offered by Lightbend Orchestration.For more information, consult the corresponding documentation for Akka Discovery integration:
For a list of the specific changes in Lagom 1.5.1, see the change log (1.5.1).
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Steve Swing, Ignasi Marimon-Clos, Dale Wijnand, Tim Moore, Alden Torres.
v1.5.0
Compare Source
We are happy to announce the availability of Lagom 1.5.0. This is the GA release of Lagom 1.5.0 and is production ready. We invite all our users to upgrade.
This version builds on top of the 2.7.x series of Play, Alpakka Kafka 1.0, and the latest improvements on Akka and Akka Management. See GitHub for the full list of commits.
Here’s a list of the most relevant improvements.
Akka Management
Akka Management is a suite of tools for operating Akka powered applications. Akka Management uses a dedicated HTTP port to expose a few routes allowing remote inspection of the state of the Akka Actor System. For example, if the process is a member of an Akka Cluster, these endpoints will report if the node already joined the cluster.
Lagom exposes the Akka Management HTTP port out of the box. Lagom will add Health Check routes by default. You can reuse library provided health checks or plugin your own. For example, Lagom uses cluster status to determine when the node is healthy. This is called Cluster Membership Check and is provided by the Akka Cluster HTTP Management library.
Another improvement Lagom 1.5 introduces, thanks to the adoption of Akka Management, is the simpler, more robust cluster formation via Akka Cluster Bootstrap. Instead of using a static list of seed nodes or relying on convoluted custom scripts to build the list of seed nodes dynamically, Cluster Bootstrap discovers the existing nodes via plugins adapting Akka Cluster Bootstrap to your orchestration environment (e.g. Kubernetes, Marathon). A static list of seed nodes is still supported but we recommend migrating to Cluster Bootstrap.
Deployment with Kubernetes or Red Hat OpenShift
Lagom 1.5.0 will no longer support Lightbend Orchestration (which was Incubating). Despite accelerating the first deployment, using Lightbend Orchestration was producing friction and reducing flexibility to tune the deployment. Moving forward, there will be no automated handling of the deployment and the suggested way is to manually maintain the production settings, the deployment descriptors and related scripts.
If you are targeting OpenShift or Kubernetes environments the new Guide to Deploy Lightbend Applications covers all the steps and details (including a sample application) to set up and tune your system.
Akka gRPC integration
Lagom 1.5.0 introduces incubating support for Akka gRPC for cross-service communication. The original HTTP/JSON-based transport is not disappearing but, instead, Lagom introduces gRPC so users can choose to expose alternative transports increasing the adoption of their services.
This feature drove some smaller improvements which non-gRPC users will also welcome.
Lagom already supported HTTP/2 since it is built on top of Play. In Lagom 1.5 we’ve reviewed all the necessary pieces so HTTP/2 can also be used on dev mode. In the same spirit, it is now also possible to use encrypted (TLS) communication on dev mode.
As a final improvement driven by the adoption of gRPC, Lagom 1.5 now supports Additional Routers (Java API / Scala API), which lets you embed any vanilla Play Router into a Lagom service. You are now able to easily reuse the Play and Akka building blocks whenever the Lagom API is not enough to complete the task at hand. Using Additional Routers it is trivial to reuse Play code you already had or extend Lagom with low-level features supported in Play but not exposed in Lagom directly (such as uploading files).
Couchbase Persistence Support
Lagom 1.5 also offers optional support for Couchbase as a new database option for persistent entities and read side processors through the Akka Persistence Couchbase module. Currently available in an Incubating early access release, Akka Persistence Couchbase has been built to work with Lagom 1.5 and the 1.0 release is coming soon. See the documentation for Couchbase Persistent Entities and Couchbase Read-Side support for more details.
Migrating from previous versions
This release introduces very little changes over the
1.5.0-RC2
so if you already moved to that version the upgrade should be trivial. If you are still using Lagom1.4.x
we recommend you first migrate to the latest version available of Lagom 1.4 series and then migrate to Lagom 1.5. If you are using a version older than1.4.x
, you should migrate one version at a time. For example: from1.3.9
to1.3.11
(because1.3.11
is1.3.latest
), then from1.3.11
to1.4.latest
and finally to1.5.x
. Read the appropriate release notes and migration guides (Java / Scala) on each step.Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.15
Compare Source
The Play Team is pleased to announce the release of Lagom Framework 1.4.15. This is the latest stable release of Lagom 1.4.x series.
Lagom 1.4.15 includes a backport of https://github.com/lagom/lagom/pull/2161 to fix a problem that appears when running tasks across multiple Scala versions, for example,
sbt +publishLocal
. There are also minor internal changes and documentation fixes. For a list of the specific changes in Lagom 1.4.15 see the change log (1.4.15).Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Play core team’s efforts. Lightbend offers commercial support for Lagom.
v1.4.14
Compare Source
The Play Team is pleased to announce the release of Lagom Framework 1.4.14. This is the latest stable release of Lagom 1.4.x series.
Lagom 1.4.14 includes a backport of https://github.com/lagom/lagom/pull/1773. Special thanks to @ihostage for the fix.
For a list of the specific changes in Lagom 1.4.14 see the change log (1.4.14).
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Play core team’s efforts. Lightbend offers commercial support for Lagom.
v1.4.13
Compare Source
The Play Team is pleased to announce the release of Lagom Framework 1.4.13. This is the latest stable release of Lagom 1.4.x series.
Lagom 1.4.13 brings in Play 2.6.23 and a new version of play-ws (v1.1.13) that includes an important bug fix on streamed calls. In case of an error, after a connection is established, the error is now properly propagated. See playframework/play-ws#340
For a list of the specific changes in Lagom 1.4.13 see the change log (1.4.13).
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Play core team’s efforts. Lightbend offers commercial support for Lagom.
v1.4.12
Compare Source
These releases bring into Lagom a new
Service Locator
implementation, based on Akka's Service Discovery. This component was previously released as an apart library, lagom-akka-discovery-service-locator, and intended to be a replacement for the Service Locator previously offered by Lightbend Orchestration.In order to allow a smoother transition for Lagom 1.4 users, we decided to include it in 1.4.12. So users can choose to first migrate their Lagom 1.4 application to Akka Service Discovery and then to Lagom 1.5. Of course, this is not a required step. It is also possible to migrate directly from Lagom 1.4 and Lightbend Orchestration to Lagom 1.5 and Akka Service Discovery.
For more information, consult the corresponding documentation for Akka Discovery integration:
For a list of the specific changes in Lagom 1.4.12 see the change log (1.4.12).
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Steve Swing, Ignasi Marimon-Clos, Dale Wijnand, Tim Moore, Alden Torres.
v1.4.11
Compare Source
The Lagom team has released Lagom 1.4.11.
This release upgrades Akka to resolve a compatibility problem with Lightbend Orchestration 1.7.3.
Highlights
If you are a user of Lightbend Orchestration you will have to upgrade your dependency of the
sbt-reactive-app
plugin to1.7.3
.See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.11 milestone.
Updating a Lagom project to version 1.4.11
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.10
Compare Source
The Lagom team has released Lagom 1.4.10.
This release upgrades Play (and transitively upgrades Akka and Akka HTTP) and Scala.
Highlights
If you are a user of Lightbend Orchestration you will have to upgrade your dependency of the
sbt-reactive-app
plugin to1.6.1
.See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.10 milestone.
Updating a Lagom project to version 1.4.10
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.9
Compare Source
This release provides a few bug fixes and an improvement.
Highlights
LagomClientFactory
introduced on the1.4.x
series which was causing aLagomClientFactory
running inside a Lagom service to interfere with the service in some scenarios causing failures at boot time.See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.9 milestone.
Updating a Lagom project to version 1.4.9
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.8
Compare Source
The Lagom team has released Lagom 1.4.8.
This release provides a bug fix and an improvement.
Highlights
random-number-generator
. See the Akka announcement for more details.See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.8 milestone.
Updating a Lagom project to version 1.4.8
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.7
Compare Source
This release provides several bug fixes and updates.
Highlights
globalPrepare
, making it more resilient.See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.7 milestone.
Updating a Lagom project to version 1.4.7
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.6
Compare Source
This release provides several bug fixes and updates.
Highlights:
See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.6 milestone.
Updating a Lagom project to version 1.4.6
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.5
Compare Source
This release provides several bug fixes and updates.
Highlights:
application.conf
with H2 (#1297)See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.5 milestone.
Updating a Lagom project to version 1.4.5
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Updating to sbt 1.x
Support for sbt 1.x was quietly released with Lagom 1.4.0, but at the time we had not yet thoroughly tested it with Lagom, so we did not yet document this support or recommend it for most users.
Some adventurous users have been using it since then, and in the meantime we have updated all of our example applications and new project templates. Since we haven't encountered any new problems with sbt 1.x, we now recommend it for all users of Lagom with sbt.
You can update the sbt version in the
project/build.properties
file. The most recent version at the time of this writing is 1.1.5.You might also need to update other plugins, global configuration, or custom build configuration. See the sbt documentation for details on migrating from version 0.13.x.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release:
v1.4.4
Compare Source
This release provides a fix for #1250.
#1250 only affects Lagom projects making usage of JDBC persistence layer, being it for the journal and/or for read-side tables.
Dependencies upgrades
Slick 3.2.3 special note
Since Slick 3.2.2, the
maxConnections
must equalnumThreads
. This is to prevent some situations where a deadlock could occur. A warning will be emitted in casemaxConnections > numThreads
and a runtime exception will be thrown ifmaxConnections < numThreads
. Therefore the best possible configuration ismaxConnections == numThreads
. See https://github.com/slick/slick/pull/1855 for detailed information.These values are configured by Lagom automatically under the configuration key
db.default.async-executor
.If you haven't changed the settings for your
async-executor
, you have nothing to do. However, if you have configured youraync-executor
with other values, you should review it and make sure thatmaxThreads == maxConnections
.See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.4 milestone.
Updating a Lagom project to version 1.4.4
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.
v1.4.3
Compare Source
Due to a mistake during the release process this release can be ignored. It's exactly the same as 1.4.2.
v1.4.2
Compare Source
This release provides a few bug fixes and minor improvements over what 1.3.11 provides already (see the summary above). As an overview, this release contains the following:
See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.2 milestone.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with the release 1.4.2:
v1.4.1
Compare Source
This release provides a few bug fixes and minor improvements. As an overview, this release contains the following:
SaveSnapshotSuccess
from showing up in unhandled messages. (#1209)See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.1 milestone.
Updating a Lagom project to version 1.4.1
To update an sbt project, change the version of
lagom-sbt-plugin
in yourproject/plugins.sbt
file.To update a Maven project, change the
lagom.version
property in your top-levelpom.xml
.After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.
Credits
Thanks to the community for their detailed bug reports and contributions.
Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.
Special thanks to the following contributors who helped with this release: