ppkarwasz commented on issue #2995: URL: https://github.com/apache/logging-log4j2/issues/2995#issuecomment-2365262162
> Worse, we've released 2 betas of 3.0 and `logging-log4j-jakarta` has been released 0 times. There is zero versions of `log4j-jakarta-jms` on Maven Central. > > If we had kept it all in one place, we would not be in this mess :-( We don't have a Jakarta JMS mainly because, I don't have enough experience with JMS to make meaningful contribution to its 3.0 version. I would need your help and expertise to: - Merge the documentation of the [2.x JMS Appender](https://logging.apache.org/log4j/2.x/manual/appenders/message-queue.html#JmsAppender) into the documentation of the [3.x JMS Appender](https://logging.staged.apache.org/log4j/jakarta/log4j-jakarta-jms.html). - Explain what JNDI parameters (like [`factoryName`](https://logging.apache.org/log4j/2.x/manual/appenders/message-queue.html#JmsAppender-attr-factoryName)) should the user provide to use JNDI safely. Should we even keep these JNDI parameters or should the runtime environment take care of that? - Explain why should users use the JMS Appender instead of [`activemq-log4j-appender`](https://github.com/apache/activemq/tree/main/activemq-log4j-appender). What are the differences between the two? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
