How can i resolve this error build

Compilation failed: java.lang.UnsupportedOperationException: Could not execute process ‘mvnw’: program not found. $PATH is ‘/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin’

Hello Sylvian,

Can you specify a bit more information, are you using Enterprise Cloud or the On-Prem version?

If on premise can you provide your Gatling and Gatling Enterprise versions?

Could you please share your pom.xml and the build option you’ve selected in your Simulation config?

This is a similar issue and the issue was a PATH was missing a config file.

All the best,
Pete

Please @GatlingPete where can i check missing config file ?

Hi @Sylvain,

As this topic is in Gatling Enterprise section, I guess this is about self hosted in the simulation configuration when you try to configure how to build it.

Did you try with ./mvnw? Usually, mvnw point to the maven wrapper. For instance the one in the root directory of our demo. And this is not globally installed.
On the other hand, you may want to use the installed version: go with mvn (without the leading “w”).

In the rare case you installed a maven wrapper distribution on your injector, you will need to add the directory to the PATH environment variable.

Does that help?
Cheers!

it is On-prem Version, Gatling version : 3.9.5 , Gatling enterprise 1.18.5

Pom

<properties>
    <!-- use the following if you're compiling with JDK 8-->
    <!-- <maven.compiler.source>1.8</maven.compiler.source>-->
    <!-- <maven.compiler.target>1.8</maven.compiler.target>-->
    <!-- comment the 2 lines above and uncomment the line bellow if you're compiling with JDK 11 or 17 -->
    <maven.compiler.release>11</maven.compiler.release>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <gatling.version>${project.version}</gatling.version>
    <gatling-maven-plugin.version>4.3.0</gatling-maven-plugin.version>
    <maven-compiler-plugin.version>3.10.1</maven-compiler-plugin.version>
    <maven-jar-plugin.version>3.2.2</maven-jar-plugin.version>
  </properties>

  <dependencies>
    <dependency>
      <groupId>io.gatling.highcharts</groupId>
      <artifactId>gatling-charts-highcharts</artifactId>
      <version>${gatling.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>org.apache.commons</groupId>
        <artifactId>commons-lang3</artifactId>
        <version>3.12.0</version>
    </dependency>
    <dependency>
      <groupId>com.google.code.gson</groupId>
      <artifactId>gson</artifactId>
      <version>2.10.1</version>
    </dependency>
  </dependencies>


  <build>
    <plugins>
      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>${maven-compiler-plugin.version}</version>
      </plugin>
      <plugin>
        <artifactId>maven-jar-plugin</artifactId>
        <version>${maven-jar-plugin.version}</version>
      </plugin>
      <plugin>
        <groupId>io.gatling</groupId>
        <artifactId>gatling-maven-plugin</artifactId>
        <version>${gatling-maven-plugin.version}</version>
        <configuration>
          <!-- Enterprise Cloud (https://cloud.gatling.io/) configuration reference: https://gatling.io/docs/gatling/reference/current/extensions/maven_plugin/#working-with-gatling-enterprise-cloud -->
          <!-- Enterprise Self-Hosted configuration reference: https://gatling.io/docs/gatling/reference/current/extensions/maven_plugin/#working-with-gatling-enterprise-self-hosted -->
        </configuration>
      </plugin>
    </plugins>
  </build>

Hello Sylvian,

We’re working on the Enterprise Support Portal on this issue with you I believe :slight_smile:

When that’s the case we prefer to centralize there to avoid confusion.

We’ll close this and continue there.

All the best,
Pete

1 Like