What about (re)moving the classes which actually depends on Jackson
(AbstractJacksonLogEventParser, JsonLogEventParser, XmlLogEventParser,
YamlLogEventParser), but keeping the interfaces (LogEventParser,
TextLogEventParser, ParseException) in log4j-core?
/Mikael
On 2024-01-05 11:25, Volkan Y
Then users or 3rd parties can implement their own parsers if they need to.
It might be useful to have parsers for some common formats like GELF,
Logstash or RFC-5424, and that can be implemented without using Jackson
if necessary.
/Mikael
On 2024-01-07 10:38, Mikael Ståldal wrote:
What abou
Hi all,
Due to the holiday season, work on Log4j has slowed down, but never
stopped. In the past two weeks we had:
## Completed work
* Jackson has been removed from the 3.x version of Log4j Core. The
YAML configuration was moved to `log4j-config-yaml` (PR#2142 [1]), the
rest rewritten with JsonR
Hi,
On Sun, 7 Jan 2024 at 20:02, Piotr P. Karwasz wrote:
> ## External activities
* The PR on adding external references to the CycloneDX SBOM (e.g. the
URLs for VDR/VEX files) has been discussed and reviewed and is ready
to be merged.
Piotr
[1] https://github.com/CycloneDX/cyclonedx-maven-plu
