# Which to use: gatling.sh, mvn, or sbt?

**URL:** <https://community.gatling.io/t/which-to-use-gatling-sh-mvn-or-sbt/2481>\
**Category:** Gatling (Open-Source)\
**Created:** [August 20, 2015, 7:18pm UTC](https://community.gatling.io/t/which-to-use-gatling-sh-mvn-or-sbt/2481 "2015-08-20T19:18:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jarrowwx](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@jarrowwx](https://community.gatling.io/u/jarrowwx)\
**Post date:** [August 20, 2015, 7:18pm UTC](https://community.gatling.io/t/which-to-use-gatling-sh-mvn-or-sbt/2481/1 "2015-08-20T19:18:52Z")

</div>

I’m getting ready to massively refactor my Gatling code base. This is an excellent opportunity to make fundamental changes to how I do things, if warranted.

Currently, I use a hosted virtual machine that I ssh into, and launch Gatling using a script. That script uses gatling.sh. I do not execute from an IDE, because doing so tends to saturate our network connection, which is a “Bad Thing”.

Is there any compelling reason to use Maven or SBT for build/execution, given how I use Gatling?