Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Doc: Gatling 3 migration
See original GitHub issue- New WebSocket API, see #3071 (first version shipped in 3.0.0-M1)
- Dropping
PerMillion, see #2873 - strict vs not strict inequalities in Assertions, see #2993
baseUrlsare now sticky, see #3043Validation#getwas removed, see #3189- new Pebble based templating engine, see #3028
- Now using Scala 2.12, see #3179
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Migrating from 2.3 to 3.0 - Gatling
Migrating from 2.3 to 3.0. Core#. JsonPath check's ofType now deep converts to Scala Map and Seq , so you'll no longer get...
Read more >Migrating from 3.7 to 3.8 - Gatling
Migrating from 3.7 to 3.8. Gatling 3.8 is not binary compatible with previous versions. Any code compiled with a previous version must be...
Read more >Upgrading from 3.6 to 3.7 - Gatling
Gatling upgrade guide from 3.6 to 3.7. ... In order to upgrade, you'll have to add the scala-maven-plugin , as described in the...
Read more >Migrating from 3.4 to 3.5 - Gatling
Gatling 3.5 is now compiled against Scala 2.13, which is not binary compatible with Scala 2.12. Any code compiled with a previous version...
Read more >Upgrading - Gatling
Upgrading. Migrating From 3.7 to 3.8 · Migrating From 3.6 to 3.7 · Migrating From 3.4 to 3.5 · Migrating From 3.3 to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Is there any workaround? I would like to migrate our project to Scala 2.12 and gatling is currently the only one dependency, which is still using 2.11.
any progress? thanks!