THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Set up your custom plug-in project
- Create a new Java project
- Add jmeter-trunk to project dependencies
- Create bin/ and src/ folders
- Create the src/jmeter.properties in the bin/ file
- This defines where JMeter internal class loader looks for classes
- It should look like this (please note that you have to adapt the first part of the search_paths property so it points to your JMeter Eclipse project!)
| No Format |
|---|
# JMeter uses case sensitive string matching to test these paths against absolute class path.
# This is very bad since paths must be *exactly* here as they appear in Java classpath.
# Hopefully this will be fixed in the future versions. Note Windows needs to escape \ character as \\.
search_paths=C:\\icecom\\jmeter-2.2\\bin;.
# File that holds a record of name changes for backward compatibility issues
upgrade_properties=upgrade.properties
# Should JMeter automatically load additional JMeter properties?
# File name to look for (comment to disable)
user.properties=user.properties
# Should JMeter automatically load additional system properties?
# File name to look for (comment to disable)
system.properties=system.properties
log_level.jorphan=WARN
log_level.jmeter.testbeans=WARN
log_level.jmeter.gui=WARN
log_level.jmeter.engine.util=WARN
log_level.jmeter.threads.util=WARN
log_level.fi.xxx=TRACE
# Widen default log output for Eclipse console
log_format=%-6.6{priority} (%-10.10{thread}) [%-25.25{category}] %{message}
.
|
- Create the src/log4j.conf in src/ file
| No Format |
|---|
log4j.rootLogger=debug, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout # Pattern to output the caller's file name and line number. log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n |
...