You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Running a particular unit/integration test with log4j output ###
53
-
By default, there will be only small number of logs output while testing. You can adjust it by changing the `log4j.properties` file in the module's `src/test/resources` directory.
53
+
By default, there will be only small number of logs output while testing. You can adjust it by changing the `log4j2.yml` file in the module's `src/test/resources` directory.
54
54
55
-
For example, if you want to see more logs for clients project tests, you can modify [the line](https://github.com/apache/kafka/blob/trunk/clients/src/test/resources/log4j.properties#L21) in `clients/src/test/resources/log4j.properties`
56
-
to `log4j.logger.org.apache.kafka=INFO` and then run:
55
+
For example, if you want to see more logs for clients project tests, you can modify [the line](https://github.com/apache/kafka/blob/trunk/clients/src/test/resources/log4j2.yml#L35) in `clients/src/test/resources/log4j2.yml`
@@ -121,6 +121,8 @@ Streams has multiple sub-projects, but you can run all the tests:
121
121
./gradlew tasks
122
122
123
123
### Building IDE project ####
124
+
*Note Please ensure that JDK17 is used when developing Kafka.*
125
+
124
126
*Note that this is not strictly necessary (IntelliJ IDEA has good built-in support for Gradle projects, for example).*
125
127
126
128
./gradlew eclipse
@@ -130,6 +132,11 @@ The `eclipse` task has been configured to use `${project_dir}/build_eclipse` as
130
132
build directory (`${project_dir}/bin`) clashes with Kafka's scripts directory and we don't use Gradle's build directory
131
133
to avoid known issues with this configuration.
132
134
135
+
IntelliJ Language Level awareness:
136
+
137
+
IntelliJ will automatically check Java syntax and compatibility for each module, even if the Java version is not
138
+
explicitly set in the Structure > Project Settings > Modules.
139
+
133
140
### Publishing the streams quickstart archetype artifact to maven ###
134
141
For the Streams archetype project, one cannot use gradle to upload to maven; instead the `mvn deploy` command needs to be called at the quickstart folder:
echo DEPRECATED: A Log4j 1.x configuration file has been detected, which is no longer recommended. >&2
29
+
echo To use a Log4j 2.x configuration, please see https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html#Log4j2ConfigurationFormat for details about Log4j configuration file migration. >&2
30
+
echo You can also use the \$KAFKA_HOME/config/connect-log4j2.yaml file as a starting point. Make sure to remove the Log4j 1.x configuration after completing the migration. >&2
echo DEPRECATED: A Log4j 1.x configuration file has been detected, which is no longer recommended. >&2
29
+
echo To use a Log4j 2.x configuration, please see https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html#Log4j2ConfigurationFormat for details about Log4j configuration file migration. >&2
30
+
echo You can also use the \$KAFKA_HOME/config/connect-log4j2.yaml file as a starting point. Make sure to remove the Log4j 1.x configuration after completing the migration. >&2
echo DEPRECATED: A Log4j 1.x configuration file has been detected, which is no longer recommended. >&2
29
+
echo To use a Log4j 2.x configuration, please see https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html#Log4j2ConfigurationFormat for details about Log4j configuration file migration. >&2
30
+
echo You can also use the \$KAFKA_HOME/config/connect-log4j2.yaml file as a starting point. Make sure to remove the Log4j 1.x configuration after completing the migration. >&2
0 commit comments