Skip to content

Latest commit

 

History

History
99 lines (64 loc) · 3.81 KB

CONTRIBUTING.md

File metadata and controls

99 lines (64 loc) · 3.81 KB
Raw

How to contribute

Want to show Apache JMeter some love? Help out by contributing!

🪲 Found a bug

Log it in our bugzilla:

  • https://jmeter.apache.org/issues.html
  • 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.

❓ Need help

Simply contact:

📊 What needs to be developed

See:

Development setup

Gradle

You might find useful Gradle commands in gradle.md

IntelliJ IDEA

You require IntelliJ 2018.3.1 or newer.

  1. Open the build.gradle.kts file with IntelliJ IDEA and choose Open as Project
  2. Make sure Create separate module per source set is selected
  3. Make sure Use default gradle wrapper is selected
  4. In the File already exists dialogue, choose Yes to overwrite
  5. In the Open Project dialogue, choose Delete Existing Project and Import

Eclipse

Eclipse can import Gradle projects automatically via Import...->Gradle project wizard.

Optionally you can generate Eclipse project by running

./gradlew eclipse

The steps to import the sources (based on Eclipse 2019-06) into Eclipse are as follows:

  1. Install Eclipse IDE for Java Developers
  2. Install the Groovy Eclipse plugin and select Groovy Compiler 2.4 (some tests are written in Groovy)
  3. Install Kotlin for Eclipse plugin (builds scripts are written in Kotlin)
  4. Make sure you have a Java 8 compatible JDK configured in your workspace
  5. Open File->Import...
  6. Select Existing Gradle Project and click Next
  7. Read How to experience the best Gradle integration and click Next
  8. Then you might just click Finish

🌟 Have a patch

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 bugzilla.

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!

❤️ Adding something new

We do love to enhance Apache JMeter with you to become more powerful! The best way to workout 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 :)

📕 Want to write docs

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).