Yeah, something like those probably make more sense, otherwise for
consistency it would have to be something like "logbackbackend", which
doesn't really roll off the tongue.
On 5/21/18 16:41 , Karl Pauls wrote:
Hm, not sure I like that name too much. It seems to be potentially
somewhat confusing.
How about:
org.apache.felix.log.logback
or maybe just:
org.apache.felix.logback
regards,
Karl
On Sat, May 19, 2018 at 12:43 AM, Raymond Auge <raymond.a...@liferay.com> wrote:
So far I've come up with what I believe is better:
org.apache.felix.logbackend
- Ray
On Thu, May 17, 2018 at 2:11 PM, Raymond Auge <raymond.a...@liferay.com>
wrote:
Hello all,
I'm going to start committing the osgi.to.logback module but I want to
make sure I have the right name since once it's sticks it will be for a
long time.
Right now it's, well... osgi.to.logback
_What it is_ is a bundle which:
- connects an OSGi Log Service (one which implements OSGi Log 1.4 spec) to
the logback backend
- provides a slf4j impl
- provides a robust and flexible backend (i.e. appenders)
- provides a bridge from logback's configuration to LoggerAdmin
- provides "framework hook" so that it can live on the classpath of the
framework for immediate logging
Suggestions for names? I will wait until Tuesday before making a real
commit so that people have a chance to pipe in then I'll pull the trigger.
Sincerely,
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>
(@OSGiAlliance)
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
