I’m getting errors trying to run the gatling maven plugin. Output attached.
out.txt (85.1 KB)
Stephane did some changes yesterday indeed:
https://github.com/excilys/gatling/commit/ce8a2177cf4acb03cf30dba17826cb20b73e5ba8#diff-5af272ebc8fdfc5775e6df8cd7302747
and
https://github.com/excilys/gatling-maven-plugin/commit/b8bf2645ce78ed9c1f14eac9e5704924cc44a06a
Are all your snapshots up to date ?
Yup - I have the poms configured to always update the jars when running.
–Spencer
Hi Spencer,
Yes, I changed the way the CLI constants are defined.
Gatling and maven plugin codes are properly aligned, the thing is that we still haven’t managed to make deploy update the maven metadatas.
@pdalpra is supposed to work on this (use https://github.com/arktekk/sbt-aether-deploy) but he’s been very sick for one week.
If someone has experience with this (deploy on Sonatype w/ sbt-aether-deploy), please raise a hand.
In your case, the workaround is to force maven plugin and gatling updates. Probably remove from your local repo.
From what I see in the logs, the maven plugin is up to date (as expected, as deploy is not done by sbt), but not gatling jars.
I deleted the io/gatling directory out of my m2 repo.
That got everything running again.
I have no idea why gatling-maven-plugin was updated but nothing else was 
–Spencer
Because the maven plugin is obviously published with maven/aether, so that the maven metadata get properly updated on the repo.
Gatling core modules are published with sbt, that doesn’t properly update the metadatas, so maven doesn’t detect the update.
We haven’t found a solution so far.