Want to show Apache JMeter some love? Help out by contributing!
Log it in GitHub issues:
- https://github.com/apache/jmeter/issues
- or send a note to the user mailing list.
Be sure to include all relevant information, like the versions of JMeter you’re using as long as Java version. A Test plan that caused the issue as well as any error messages are also very helpful.
Contact:
- Our users mailing list
- or ask question on stackoverflow.
See:
You might find useful Gradle commands in gradle.md
You require IntelliJ 2018.3.1 or newer.
- Open the build.gradle.kts file with IntelliJ IDEA and choose
Open as Project
- Make sure
Create separate module per source set
is selected - Make sure
Use default gradle wrapper
is selected - In the
File already exists
dialogue, chooseYes
to overwrite - In the
Open Project
dialogue, chooseDelete Existing Project and Import
Eclipse can import Gradle projects automatically via Import...->Gradle project
wizard.
Optionally you can generate an Eclipse project by running
./gradlew eclipse
The steps to import the sources (based on Eclipse 2019-06) into Eclipse are as follows:
- Install
Eclipse IDE for Java Developers
- Install
Kotlin for Eclipse
plugin (JMeter code uses Java and Kotlin) - Make sure you have a Java 17 compatible JDK configured in your workspace
- Open
File->Import...
- Select
Existing Gradle Project
and clickNext
- Read
How to experience the best Gradle integration
and clickNext
- Then you might just click
Finish
The best way to make sure your issue or feature is addressed is to submit a patch. We accept patches through:
- pull requests
- patch attached to JMeter developers mailing list.
However, before sending a patch, please make sure that the following applies:
- Your commit message is descriptive.
- Your patch doesn't have useless merge commits.
- Your coding style is similar to ours.
- Your patch is 100% tested. JUnit are welcome.
- All tests checks pass (run
./gradlew check
) - You understand that we're very grateful for your patch!
We do love to enhance Apache JMeter with you to become more powerful! The best way to work out your idea is to discuss it first at our dev mailing list:
Please, if you can, don't just throw us the code of a new feature; lets figure first together what would be the best approach regarding the current architecture and future plans, before any development. This way we all get sure that your idea is aligned with the codebase, and you can enjoy your happy coding even more :)
Documentation is very valuable to us.
It is located in xdocs folder in XML format.
You can contribute as you would for code through patch or PR (pull request).