# Set own "binaries" at configuration does not work properly

**URL:** <https://community.gatling.io/t/set-own-binaries-at-configuration-does-not-work-properly/181>\
**Category:** Gatling (Open-Source)\
**Created:** [November 29, 2012, 2:03pm UTC](https://community.gatling.io/t/set-own-binaries-at-configuration-does-not-work-properly/181 "2012-11-29T14:03:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Danny\_Lade](https://avatars.discourse-cdn.com/v4/letter/d/71c47a/32.png) [@Danny\_Lade](https://community.gatling.io/u/Danny_Lade)\
**Post date:** [November 29, 2012, 2:03pm UTC](https://community.gatling.io/t/set-own-binaries-at-configuration-does-not-work-properly/181/1 "2012-11-29T14:03:30Z")

</div>

I tried to set the “binaries” configuration to change the “target” directory. Without this setting the simulation works just fine (got compiled at GATLING\_HOME/target and started normally).  
But otherwise I get:

Exception in thread “main” java.lang.ClassNotFoundException: loadtest.TestSimulation  
at java.net.URLClassLoader$1.run(Unknown Source)

Here’re my settings:

gatling {  
simulation {  
class = loadtest.TestSimulation  
}  
directory {  
data = …/src/loadtest/resources/data  
requestBodies = …/src/loadtest/resources/request-bodies  
simulations = …/src/loadtest/scala  
results = …/target/loadtest/results  
binaries = …/target/loadtest  
}  
}

Regards Danny

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [November 29, 2012, 2:19pm UTC](https://community.gatling.io/t/set-own-binaries-at-configuration-does-not-work-properly/181/2 "2012-11-29T14:19:04Z")

</div>

How do you run? From the command line, from the maven plugin?

---

<div class="post-metadata">

**Author:** ![Danny\_Lade](https://avatars.discourse-cdn.com/v4/letter/d/71c47a/32.png) [@Danny\_Lade](https://community.gatling.io/u/Danny_Lade)\
**Post date:** [November 29, 2012, 2:56pm UTC](https://community.gatling.io/t/set-own-binaries-at-configuration-does-not-work-properly/181/3 "2012-11-29T14:56:51Z")

</div>

Currently I run it over the command line (the maven plugin is planned to be used later).

---

<div class="post-metadata">

**Author:** ![Excilys](https://avatars.discourse-cdn.com/v4/letter/e/8797f3/32.png) [@Excilys](https://community.gatling.io/u/Excilys)\
**Post date:** [November 29, 2012, 3:30pm UTC](https://community.gatling.io/t/set-own-binaries-at-configuration-does-not-work-properly/181/4 "2012-11-29T15:30:15Z")

</div>

In your case, you shouldn’t force the binaries folder. It’s used to tell Gatling that the classes have already been compiled, and where, and that it should skip the compiling phase. It’s intended for the projects generated from the maven archetype, where compiling is done by the IDE.

---

<div class="post-metadata">

**Author:** ![Danny\_Lade](https://avatars.discourse-cdn.com/v4/letter/d/71c47a/32.png) [@Danny\_Lade](https://community.gatling.io/u/Danny_Lade)\
**Post date:** [November 29, 2012, 4:04pm UTC](https://community.gatling.io/t/set-own-binaries-at-configuration-does-not-work-properly/181/5 "2012-11-29T16:04:23Z")

</div>

Thanks for the advice.  
Furthermore if I use the maven plugin I don’t need to use this config anymore (seen in the documentation).

Regards Danny