# Error accessing other maven module by dependencies?

**URL:** <https://community.gatling.io/t/error-accessing-other-maven-module-by-dependencies/186>\
**Category:** Gatling (Open-Source)\
**Created:** [December 4, 2012, 9:59am UTC](https://community.gatling.io/t/error-accessing-other-maven-module-by-dependencies/186 "2012-12-04T09:59:43Z")\
**Posts on this page:** 4\
**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:** [December 4, 2012, 9:59am UTC](https://community.gatling.io/t/error-accessing-other-maven-module-by-dependencies/186/1 "2012-12-04T09:59:43Z")

</div>

Its me again 🙂

I’ve got the following situation:

- I work on a multi module environment configured via maven
- therefore I’ve got a “utils” module (written in Java) with some crazy stuff inside and a “load test” module (written in Scala) for gatling
- I’d need some of the utils in the “load test” module (reading special config etc.), so I’ve configured dependencies to “utils” module

But all I get is a compilation error:  
[INFO] 10:33:17.180 [main][ERROR][slf4j.scala:105] c.e.e.g.a.ZincCompiler$ - project-load-test\src\loadtest\scala\net\company\project\loadtest\config\LoadTestConfiguration.scala:6: object util is not a member of package net.company.project  
[INFO] 10:33:17.182 [main][ERROR][slf4j.scala:105] c.e.e.g.a.ZincCompiler$ - import net.company.project.util.Version  
[INFO] 10:33:17.188 [main][ERROR][slf4j.scala:105] c.e.e.g.a.ZincCompiler$ - ^

It neither works with the CLI nor calling “mvn gatling:execute”.

How can I solve this?

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:** [December 4, 2012, 10:56am UTC](https://community.gatling.io/t/error-accessing-other-maven-module-by-dependencies/186/2 "2012-12-04T10:56:47Z")

</div>

Have you tried adding the dep to the plugins deps, not the project one?

---

<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:** [December 4, 2012, 1:47pm UTC](https://community.gatling.io/t/error-accessing-other-maven-module-by-dependencies/186/3 "2012-12-04T13:47:53Z")

</div>

It seems to work though - but I had to import it for project AND plugin.  
Within the project the dependencies can be solved for the editor and within the plugin for the gatling runtime.

Many thanks,  
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:** [December 4, 2012, 1:51pm UTC](https://community.gatling.io/t/error-accessing-other-maven-module-by-dependencies/186/4 "2012-12-04T13:51:05Z")

</div>

The gatling maven plugin is based on ant (seemed a convenient wait to set  
up distinct JVM options).  
It would be great if we could find a way to propagate the project test  
classpath to Gatling.

Will try, stay tuned.

Steph