That's right - we don't bundle in a JMS jar, although users can add one to the classpath to use the JMSReceiver.
On 11/12/17, Mikael Ståldal <mi...@apache.org> wrote: > When running Chainsaw, I see this error message: > > Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks > like a dependent class is missing from the classpath > java.lang.NoClassDefFoundError: javax/jms/MessageListener > > It seems to work anyway (without JMX support I suppose) though. But I > guess some jar file with that class should be on the classpath? > > > On 2017-11-10 20:00, Matt Sicker wrote: >> This is a vote to release Apache Chainsaw 2.0.0-rc1. >> >> (Note: I've created release instructions on the new wiki: < >> https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>) >> >> Artifacts: >> https://dist.apache.org/repos/dist/dev/logging/chainsaw/ >> svn revision 23048 >> >> Site: >> http://musigma.org/chainsaw-site/ >> >> Git: >> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git >> tag: chainsaw-2.0.0-rc1 >> >> All artifacts have been signed by my PGP key >> id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging >> KEYS >> file. >> >> This vote will be open for at least 72 hours and requires at least 3 +1 >> votes and more +1 votes than -1 votes. >> > >
