[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [equinox-dev] log4j in OSGi clarification
- From: "Kaegi, Simon" <Simon.Kaegi@xxxxxxxxxx>
- Date: Fri, 23 Jun 2006 14:56:05 -0400
- Delivered-to: firstname.lastname@example.org
- Importance: normal
- Priority: normal
- Thread-index: AcaW71gplX6XbULpR6aMPZdKJUlfuwABmx4g
- Thread-topic: [equinox-dev] log4j in OSGi clarification
Buddy policy is not needed for Log4j's internally
If you need to package custom appenders and want
to avoid Buddy-Policy you can package directly alongside in you log4j
bundle or alternately as a fragment.
Hope this helps.
I was reading the book on rich client programs for
eclipse to try to solve my log4j issue as suggested on the newsgroup
while back. I noticed that if I add a buddy policy to my log4j manifest, then
it should start to see the appenders. Is this
necessary for the appenders
that come packaged with log4j as well? I think my question is, do I need to
make a bundle
for the console appender, the file appender, etc. and tell
them that they are buddies for log4j? Thanks,
This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.