As long as we can get those security issues released, I am fine.
Personally I am fine with helping with the editor, if it stays as web app (I
can do react and such).
If it's JavaFX - I am lost. I have hard time helping with Swing in Chainsaw.
Since you mentioned its importance, we should work on
Yes, I can update the dependencies and do a release.
The primary issue with the project as it stands is the Catalog Editor UI. It is
really stupid. It uses Spring Boot for the UI but it is meant to run locally.
It was suggested I switch the UI to JavaFX but I have never had the chance.
FWWI -
Log4j Audit has multiple components:
* Audit API for extending log4j-api with some additional audit logging APIs
* Tool for managing your audit event schemata and such (the web app thing)
* Tool for generating structured log classes from the event schemata
Thus, in typical use, you can (and
I think it would be nice to do a release just to update dependencies.
Gary
On Tue, Oct 10, 2023, 2:33 PM Christian Grobmeier
wrote:
> Hello,
>
> We have been talking about log4j-audit (same thread as with log4j-server).
>
> I have checked today after seeing Piotr's message, and even after
Hello,
We have been talking about log4j-audit (same thread as with log4j-server).
I have checked today after seeing Piotr's message, and even after reading the
readme, I am still trying to figure out the purpose of this product. That
aside, I am concerned the last change was four years ago.
