As we chose to push Gatling on Github, it is likely that other people will want to see how we did it, and hopefully help us; the aim of this page is to ease the "get-into-developing-gatling" process. To know how you can contribute to Gatling, visit Contributing.
Once every software is installed, you can import Gatling project into Eclipse. Doing so is really easy:
Gatling is made to run as a standalone program, thus most users will want to download a tarball containing all the binaries required to execute Gatling.
As a developer, you'll want to run Gatling from Eclipse, sparing the long process of tarball creation. These are the steps required:
GATLING_HOMEis, from a developer point of view, the folder in which you'll find the folders: assets, bin, results, etc. It could be defined as follows:
Add these arguments in the VM options:
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms512M -Xmx512M -Xmn100M -Xss512k -XX:+HeapDumpOnOutOfMemoryError -XX:+AggressiveOpts -XX:+OptimizeStringConcat -XX:+UseFastAccessorMethods -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
GATLING_HOMEin the environment tab
$GATLING_HOME/confto the classpath before
gatling-charts-highchartsto the classpath before
Another set of tools can be appreciated if you want to test things and, for example, package Gatling as an archive.