I wouldn't worry too much about the Travis build, though that looks like a bug in our config rather than anything on your end.
Anyways, about your PR. I like the idea (and the PR), though I'm wondering if it'd be useful to allow for a dynamic message key to be created based on a pattern (e.g., perhaps my key would be from some system property, so that way I could filter through a topic by key and find log messages grouped together as such). I'll have time tomorrow to look more closely at it. On 1 October 2017 at 14:21, Jorge Sánchez <[email protected]> wrote: > Hi Devs, > > I have created ticket https://issues.apache.org/jira/browse/LOG4J2-2062 in > order to improve the KafkaAppender with the possibility of including a Key > to every message sent to a Kafka topic and I have run mvn clean verify as > stated in the Contributing page with all the tests in the log4j-core module > passing. > > After that I have created a PR to merge into the main repo but the Travis > job is failing, please, can someone have a look at it? It doesn't seem > related to any code change: > Error: JAVA_HOME is not defined correctly. We cannot execute > /usr/lib/jvm/java-7-oracle/bin/java > > https://travis-ci.org/apache/logging-log4j2/jobs/281703149 > > Thank you. > -- Matt Sicker <[email protected]>
