If you just need to connect as a JMS client, you just need the activemq-client jar and its transitive dependencies. If you are using something like maven then you can add that jar to your pom file and then exclude dependencies you don't want (in this case log4j).
On Tue, Mar 29, 2016 at 2:43 PM, stak <arun.ktirum...@gmail.com> wrote: > So are you saying that activemq-all.jar is not a production grade jar to be > used as a client jar when they want to connect to an external activemq as a > client?. Is the purpose of that jar really only for a quick unit test of > sorts? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/activemq-all-jar-tight-coupling-with-log4j-tp4710022p4710030.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
