I am asking because that directory is the link provided in the vote and we
vote on sources.
Gary
On Sat, Sep 10, 2022, 17:51 Ralph Goers wrote:
> I am not sure why you asked this in the vote thread.
>
> It is empty because that is where the Kotlin releases would go while
> they are voted on and
+1
Tested against
* WildFly Core main with -DallTests ( https://github.com/wildfly/wildfly-core/ )
* JBoss Logging 3.4 branch (
https://github.com/jboss-logging/jboss-logging/tree/3.4 )
* Log4j2 JBoss Logmanager main(
https://github.com/jboss-logging/log4j2-jboss-logmanager )
Regards
Boris
> R
Gary, the `kotlin` directory is for placing release candidates for the Log4j
Kotlin API. Same with the `scala` directory there. Whenever I promote a release
candidate to a release, I use `svn mv` between dist/dev to dist/prod basically.
See step (13) in
https://cwiki.apache.org/confluence/displ
+1
Tested on combination of:
openjdk version "1.8.0_322"
OpenJDK Runtime Environment (Zulu 8.60.0.21-CA-macos-aarch64) (build
1.8.0_322-b06)
OpenJDK 64-Bit Server VM (Zulu 8.60.0.21-CA-macos-aarch64) (build 25.322-b06,
mixed mode)
openjdk version "11.0.15" 2022-04-19 LTS
OpenJDK Runtime Envir
Scoped variables are a great example! There’s a similar concept in some
reactive streams APIs (which is also a standard Java API starting in 9) with
“contexts”, and the same concept is also available in the standard Go library
in its “context” package for associating arbitrary values with string
I saw the same errors with JDK8 on Windows:
openjdk version "1.8.0_342"
OpenJDK Runtime Environment Corretto-8.342.07.3 (build 1.8.0_342-b07)
OpenJDK 64-Bit Server VM Corretto-8.342.07.3 (build 25.342-b07, mixed mode)
[ERROR] Errors:
[ERROR]
GelfLayoutTest.testLayoutNewLineDelimiter:286->testC
Hi Gary,
On Sun, 11 Sept 2022 at 18:13, Gary Gregory wrote:
>
> java.lang.IllegalStateException: Unexpected message larger than 4096 bytes
This is probably due to the 8192 bytes limit in
`EncodingListAppender.Destination`. We should probably increase it.
Piotr
I get the same error when running on java 11, too, but that’s to be expected. I
wrote that test originally to explicitly detect the point at which we’d have to
do something about it, and we already addressed the original issue long ago. In
the 2.x branch, this is handled by using Maven toolchain
