-
Notifications
You must be signed in to change notification settings - Fork 37
Developer Environment Setup
steeltomato edited this page Jan 24, 2012
·
4 revisions
- Import the JMeter project from a source distribution or from the Apache SVN site.
- Run
ant download_jars
to fetch all the required libraries. - Remove .classpath and replace with eclipse.classpath then refresh project
- Download the BlazeDS jars/src and add them to the build path for jMeter.
- Note: If targeting a specific application, it is probably a good idea to use a matching BlazeDS version.
- TODO: Turn this into an ant/maven task
- Clone the git repo to a local directory.
- Import the source into a new Eclipse project.
- Set jakarta-jmeter as a required project for jmeter-amf.
- Make a symlink called 'lib' in jmeter-amf/ and point it to jakarta-jmeter/lib.
- Refresh and add all of the libs from the jmeter project to the jmeter-amf build path.
- At this point, both projects should be without build errors.
- Copy these files from jakarta-jmeter/bin to jmeter-amf/bin:
- jmeter.properties
- saveservice.properties
- system.properties
- upgrade.properties
- user.properties
- TODO: Turn this copy into an ant task
- Edit jmeter.properties.
- In the log4j section, add
log_level.jmeter.protocol.amf=DEBUG
- Uncomment
log_file=
so that output goes to the Eclipse console - Uncomment search paths and provide a path to compiled classes,
search_paths=../build/protocol/amf;.
- Create a run configuration for jmeter-amf.
- Set working directory to
${workspace_loc:jmeter-amf/bin}
- Set the main class to org.apache.jmeter.NewDriver