Scala signature package has wrong version expected: 5.0 found: 5.2

4,040 views
Skip to first unread message

Aleksey Gruba

unread,
Mar 31, 2021, 5:26:26 AM3/31/21
to Gatling User Group
Hi, 

I would like to try Gatling and started with maven plugin in Intellij IDEA (gatling/gatling-maven-plugin-demo: Showcase of the Gatling Plugin for Maven (github.com)). When I run Engine class, there are lots of errors like this one:
scalac: error while loading package, class file '<current_user>\.m2\repository\io\gatling\gatling-app\3.5.1\gatling-app-3.5.1.jar(io/gatling/app/package.class)' is broken 
 (class java.lang.RuntimeException/error reading Scala signature of package.class: Scala signature package has wrong version
 expected: 5.0
 found: 5.2 in package.class)

As far as I understand it means that the gatling classes were compiled with higher version of scala compiler (5.2) than current scalac expects.
I use latest gatling (3.5.1) and Scala SDK 2.12.12. There was no previous installation of Scala SDK (it's my first experience with Scala at all). 

What could be a reason for these errors? 

Thanks!

Best regards, 
Aleksey. 

Sébastien BREVET

unread,
Mar 31, 2021, 5:31:43 AM3/31/21
to gat...@googlegroups.com
Hi,

Indeed, the "Installation" prerequisites documentation is misleading. (Note to self, creating a ticket about that)
3.5.0 introduced the migration to scala 2.13.

So, you have to use scala 2.13 (`2.13.5` is the latest release)

Cheers!

--
You received this message because you are subscribed to the Google Groups "Gatling User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gatling/11cbaa5e-e53a-45b6-a649-ad1b218b5e5bn%40googlegroups.com.


--
LogoSébastien BREVET
Backend engineer
site: gatling.io

Aleksey Gruba

unread,
Mar 31, 2021, 5:49:15 AM3/31/21
to Gatling User Group
Yeap, it works as expected with SDK 2.13.5. 

Thanks for help! It's good that we have found a bug in the docs :)
Reply all
Reply to author
Forward
0 new messages