Looks like the build has an issue running `mvn package` due to a
Surefire plugin problem with JDK10, due to
https://issues.apache.org/jira/browse/SUREFIRE-1439. However, even
after updating surefire, the build with JDK10 seems to fail due to
what seems like an incompatibility with the current Kotli
Did that build the source and javadoc jars as well?
On Thu, Nov 1, 2018 at 20:59, Raman Gupta wrote:
> Matt, I had no issue building the site with jdk10:
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j Kotlin API Parent 1.0.1-SNAPSHOT .. SUCCESS [
> 14.725 s]
> [INFO] Apache Log4j
Matt, I had no issue building the site with jdk10:
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j Kotlin API Parent 1.0.1-SNAPSHOT .. SUCCESS [ 14.725 s]
[INFO] Apache Log4j Kotlin API SUCCESS [ 9.741 s]
[INFO] Apache Log4j Kotlin API Samples 1.0.1-SNAPSHOT ..
Hi All:
I can't seem to get TZ offsets to print based.
See
https://issues.apache.org/jira/browse/LOG4J2-1246?focusedCommentId=16672422&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16672422
To test, edit log4j-core/src/test/resources/log4j2-console.xml and
run Con
I have pushed the garbage-free version of log4j2-logstash-layout to the
branch: https://github.com/vy/log4j2-logstash-layout/tree/json-generator
There you can also see the JMH results in a table.
On Tue, Oct 23, 2018 at 2:28 AM Remko Popma wrote:
> Looks very nice!
>
> The non garbage-free impl
It’s not the uploading I need help with. The pom config is broken
somewhere. You can test it locally by changing the deployment target to a
local instance of Nexus or Artifactory or probably even just stage it in
your local file system. In fact, running ‘mvn site’ should be enough to see
where the
