On 03/23/2010 09:20 PM, Robbie Gemmell wrote:
Alternatively, shipping the JDK bindings by default could be a viable
option, working out the box but requiring that users actually
configure java.util.logging to required behaviour.
I like this approach.
It doesn't have to be in the same location as the core jars if that is
felt to cause confusion. Perhaps e.g. bundled with examples or similar[1].
I would think that anyone who doesn't care enough to configure the
logging at all might reasonably expect not to be too surprised to
find there are none, if they ever even looked at the logs.
I think it can be frustrating for people trying to get familiar with the
project to debug simple problems with packaged examples or tools if
there is no logging available.
Not everyone who ends up trying to get something working with the JMS
client has experience with sl4j. Having to dig around on information on
what to download, where to install it and then what format of file needs
to be created is significantly harder than e.g. the python or c++
clients. Making that easier is in my view quite reasonable. Having at
least warning level messages be visible is also a help.
--Gordon
[1] I always feel like there something missing on the java side when
testing releases - no test app or examples to run.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
