So, everything stopped working for me, and I can’t sort out what’s changing.
It started out with (I think) the gatling maven plugin complaining about not having a short object in CommandLineConstans
I’ve cleared out io.gatling in my m2 repository, and that seems to have made things worse.
So - any thoughts / tips / help?
–Spencer
Which version of the gatling-maven-plugin do you use?
Please upgrade to the 2.0.0-SNAPSHOT (beware of the groupId):
https://oss.sonatype.org/content/repositories/snapshots/io/gatling/gatling-maven-plugin/2.0.0-SNAPSHOT/
We’re in the process of cleaning up our coding rules before the release, so that things are clear for people willing to contribute.
Strange…
I indeed made a change to Gatling code which affected the Maven plugin but it should work fine with the latest snapshots of Gatling and Gatling’s Maven Plugin.
Envoyé de mon iPhone
Anything look wrong with this pom?
4.0.0
io.gatling
gatling-maven-plugin-demo
2.0.0-SNAPSHOT
jar
excilys
Excilys Repository
http://oss.sonatype.org/content/repositories/snapshots/
org.scala-lang
scala-compiler
2.10.3
io.fastjson
boon
0.7
-XX:+CMSParallelRemarkEnabled
-XX:+CMSClassUnloadingEnabled
-XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly
-XX:SurvivorRatio=8
-XX:MaxTenuringThreshold=1
I don’t see anything.
What’s the problem exactly?
Oh, yes, I think that when you declare a maven repository, you have to explicitly enable fetching snapshots!
There’s disabled by default.
Could you try:
excilys Excilys Repository [http://oss.sonatype.org/content/repositories/snapshots/](http://oss.sonatype.org/content/repositories/snapshots/) trueTried it - still failing.
Just prior to this stack trace, I see the message: Compilation failed, followed by mvn boilerplate about build failure.
I get this stack trace at the end:
[ERROR] Failed to execute goal io.gatling:gatling-maven-plugin:2.0.0-SNAPSHOT:execute (default-cli) on project gatling-maven-plugin-demo: Gatling failed. Process exited with an error: 1 (Exit value: 1) → [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.gatling:gatling-maven-plugin:2.0.0-SNAPSHOT:execute (default-cli) on project gatling-maven-plugin-demo: Gatling failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Gatling failed.
at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:231)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
… 19 more
Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:402)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:164)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:151)
at io.gatling.mojo.GatlingJavaMainCallerByFork.run(GatlingJavaMainCallerByFork.java:66)
at scala_maven_executions.JavaMainCallerSupport.run(JavaMainCallerSupport.java:110)
at io.gatling.mojo.GatlingMojo.executeGatling(GatlingMojo.java:247)
at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:228)
… 21 more
What’s the timestamp of your local copy of the maven plugin?
And the one of your Gatling snapshot?
Do you run clean when you run maven?
$ cat ~/.m2/repository/io/gatling/gatling-maven-plugin/2.0.0-SNAPSHOT/maven-metadata-excilys.xml
<?xml version="1.0" encoding="UTF-8"?> io.gatling gatling-maven-plugin 2.0.0-SNAPSHOT 20140328.135658 196 20140328135658 jar 2.0.0-20140328.135658-196 20140328135658 pom 2.0.0-20140328.135658-196 20140328135658 sources jar 2.0.0-20140328.135658-196 20140328135658$ cat ~/.m2/repository/io/gatling/gatling-app/2.0.0-SNAPSHOT/maven-metadata-excilys.xml
<?xml version="1.0" encoding="UTF-8"?> io.gatling gatling-app 2.0.0-SNAPSHOT 20140322143206Just tried mvn clean and then the plugin - no difference.
Could you delete the whole gatling dir from your local .m2 cache, please?
It could as well be a broken download.
There’s something very very weird with the metadata on Sonatype:
https://oss.sonatype.org/content/repositories/snapshots/io/gatling/gatling-app/2.0.0-SNAPSHOT/
Latest binaries are from the 28th while the metadata hasn’t been updated since the 22th?!
Nope - I’m wondering if something in my code has stopped compiling, thus the reported compilation error.
Trying to get the code up in an IDE to get a better look.
Well, I can assure you - I didn’t do that 
Which version of maven do you use?
3.0.4
Running on ubuntu
I just did a test on my machine and it works fine…