Doc: Gatling 3 migration

[slandelle]

• New WebSocket API, see HTTP: New WebSocket API #3071 (first version shipped in 3.0.0-M1)
• Dropping PerMillion, see Core: Turn percent assertions to Double instead of Int #2873
• strict vs not strict inequalities in Assertions, see Core: strict vs not strict inequalities in Assertions #2993
• baseUrls are now sticky, see HTTP: make baseUrls sticky #3043
• Validation#get was removed, see Core: Remove Validation#get #3189
• new Pebble based templating engine, see Support Pebble templating engine #3028
• Now using Scala 2.12, see Upgrade Scala 2.12 #3179

[mikla]

Hi there!
When do you plan to release Scala 2.12 support?
As far as I see everything is closed except #3071.

[slandelle]

Gatling 3 should be out late 2017/early 2018

[aakavalevich]

Will Gatling 3 be the first release with Scala 2.12 support?

[slandelle]

Yep

[slandelle]

Then FrontLine has Gatling 3 previews, indeed with Scala 2.12.

[aakavalevich]

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.

[slandelle]

Don't have a single monolithic project. Either have modules with different Scala versions or move Gatling to it's own. Or subscribe to FrontLine.

[mb720]

@slandelle Can you maybe point us to a build.sbt that uses Gatling as a module, circumventing the problem with incompatible Scala versions?
Thanks!

[slandelle]

Have a look at Gatling build itself, compiler module is compiled against Scala 2.10 (old/stable Zinc version).

[magro]

What about releasing a gatling 3.0.0 RC? This way there would at least be a stable version available for early adopters...

[slandelle]

We'll release Release Candidates once Gatling 3 will be feature complete.
But we won't be releasing milestones before that. We don't really have time for that, and we had a bad experience with doing that for 2.0.0-M3a where people wouldn't upgrade to stable versions and kept bugging us with it for years.
We do provide private milestones for our FrontLine customers.
If you're not willing to contract with us, you can deploy on your own, typically on a private repo.

[magro]

Ok, thanks!

[thinkerou]

any progress? thanks!

[thinkerou]

like done, thanks!