You may find that you need to spend so much energy on your logging
abstraction that it makes you wonder why not to use jboss-logging as
your logging abstraction in the first place. Is this NIH?
-thomas
On 06/06/2012 08:32 PM, Bill Burke wrote:
On 6/6/12 2:11 PM, David M. Lloyd wrote:
> On 06/06/2012 12:35 PM, Bill Burke wrote:
>> I do not want to use the JBoss Logging annotation framework as I do not
>> want to have a hard dependency on JBoss Logging for my project.
>>
>> Is there a manual API that I can use instead to build a message?
>> Something like:
>>
>> String getMessage(long id, Object... params);
> No, there isn't (and if there were, it'd be part of JBoss Logging,
> so...). You can however use the maven-shade-plugin to slurp the JBoss
> Logging classes into your project (even under another package name).
> It's a pretty small project and we're working to make it smaller.
>
Eh, I guess I could just use reflection techniques to create my own
abstraction and stuff the logging interfaces in a separate jar.
BTW, this is ridiculously over-engineered and at least for me, harder to
adapt to my project. These engineering hours could have been better
spent elsewhere.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx