@ -201,12 +201,6 @@ If needed, you can specify the Scala version with `-PscalaVersion=2.13`.
@@ -201,12 +201,6 @@ If needed, you can specify the Scala version with `-PscalaVersion=2.13`.
### Building the test jar ###
./gradlew testJar
### Determining how transitive dependencies are added ###
### Determining if any dependencies could be updated ###
./gradlew dependencyUpdates
### Running code quality checks ###
There are two code quality analysis tools that we regularly run, spotbugs and checkstyle.
@ -233,6 +227,21 @@ We use [JMH](https://openjdk.java.net/projects/code-tools/jmh/) to write microbe
@@ -233,6 +227,21 @@ We use [JMH](https://openjdk.java.net/projects/code-tools/jmh/) to write microbe
See [jmh-benchmarks/README.md](https://github.com/apache/kafka/blob/trunk/jmh-benchmarks/README.md) for details on how to run the microbenchmarks.
### Dependency Analysis ###
The gradle [dependency debugging documentation](https://docs.gradle.org/current/userguide/viewing_debugging_dependencies.html) mentions using the `dependencies` or `dependencyInsight` tasks to debug dependencies for the root project or individual subprojects.
Alternatively, use the `allDeps` or `allDepInsight` tasks for recursively iterating through all subprojects:
These take the same arguments as the builtin variants.
### Determining if any dependencies could be updated ###
./gradlew dependencyUpdates
### Common build options ###
The following options should be set with a `-P` switch, for example `./gradlew -PmaxParallelForks=1 test`.
@ -260,18 +269,6 @@ only safe if the Scala library version is the same at compile time and runtime.
@@ -260,18 +269,6 @@ only safe if the Scala library version is the same at compile time and runtime.
may depend on the kafka jar for integration tests where they may include a scala library with a different version), we don't enable it by
default. See https://www.lightbend.com/blog/scala-inliner-optimizer for more details.
### Dependency Analysis ###
The gradle [dependency debugging documentation](https://docs.gradle.org/current/userguide/viewing_debugging_dependencies.html) mentions using the `dependencies` or `dependencyInsight` tasks to debug dependencies for the root project or individual subprojects.
Alternatively, use the `allDeps` or `allDepInsight` tasks for recursively iterating through all subprojects: