Re: Support for starting and stopping docker containers during tests
There's a new Apache Commons Testing < https://github.com/apache/commons-testing> in development where it may also be appropriate. On 16 February 2018 at 05:52, Christian Schneider <ch...@die-schneider.net> wrote: > I did some research and found these projects: > - https://github.com/geowarin/docker-junit-rule > - https://github.com/palantir/docker-compose-rule > > The first project is just a one man show but the second seems to have a > community behind it. > Both allow to start docker from the junit test. > > There is also this article from codecentric: > - https://blog.codecentric.de/en/2017/03/writing-integration-tests-docker- > compose-junit/ > > Anyway it seems that maybe there are already good libraries out there. > Does any of you have tested any of these or used something else? > > Christian > > > 2018-02-16 12:39 GMT+01:00 Christian Schneider <ch...@die-schneider.net>: > >> At Adobe we created a small project to start docker containers before a >> junit test and reliably stop them after the test. As this is of very >> general use I wonder if it would make sense to open source this. I am >> currently checking internally if we can do this. >> >> In parallel I also wanted to check if there are existing alternatives out >> there and if none are suitable as a replacement if the ops4j community >> would be interested to host such a project. >> >> I am pretty sure that there is already good support to manage docker >> instances as a maven plugin. One interesting property of our impl is that >> the start / stop of docker is controlled from java. So you can simply run >> the junit test from eclipse and it does the docker management transparently. >> >> Christian >> >> -- >> -- >> Christian Schneider >> http://www.liquid-reality.de >> >> Computer Scientist >> http://www.adobe.com >> >> > > > -- > -- > Christian Schneider > http://www.liquid-reality.de > > Computer Scientist > http://www.adobe.com > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Blocking threads in log4j appender
If you use pax-logging-log4j2, you can migrate easily, though the version of log4j2 in there is somewhat out of date. Async appender will certainly alleviate some issues, but it can't do much about APIs that publicly add the synchronized keyword to hot spots like in log4j1. On 7 November 2017 at 11:53, Andrei Shakirin <andrei.shaki...@gmail.com> wrote: > Hi Matt, > > Thanks for quick response, but I don't use log4j directly, only through > the pax-logging-service.jar. > And the issue is still there even with last released pax-logging-service > version (1.10.1). > > Async appender is an option, will definitely try that. > > Regards, > Andrei. > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Blocking threads in log4j appender
Log4j 1.x is unsupported nowadays; you should migrate to Log4j 2.x. If you're unable to migrate, then your best bet is to try to use an AsyncAppender, though those are also vastly improved in Log4j 2.x (along with far less synchronized blocks to cause problems). More info: <https://logging.apache.org/log4j/2.x/performance.html> On 7 November 2017 at 11:42, Andrei Shakirin <andrei.shaki...@gmail.com> wrote: > Hi, > > I have experienced that under high load logj4 appender (packed into > pax-logging-service.jar) blocks threads and essentially reduces the > throughput (in my case about 15%). > > The stack trace from thread dump: > > "qtp52584153-10776" - Thread t@10776 >java.lang.Thread.State: BLOCKED > at > org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:231) > - waiting to lock <6a484498> (a > org.apache.log4j.DailyRollingFileAppender) owned by "ArticlePAAThread" t@10014 > at > org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:59) > at org.apache.log4j.Category.callAppenders(Category.java:179) > at org.apache.log4j.Category.forcedLog(Category.java:333) > at org.apache.log4j.Category.log(Category.java:724) > at > org.ops4j.pax.logging.service.internal.PaxLoggerImpl.inform(PaxLoggerImpl.java:167) > at > org.ops4j.pax.logging.internal.TrackingLogger.inform(TrackingLogger.java:86) > at org.ops4j.pax.logging.slf4j.Slf4jLogger.info(Slf4jLogger.java:534) > at > xxx.LoggingServiceExecutionTimeHandler.filter(LoggingServiceExecutionTimeHandler.java:52) > > > > The issue is discussed in log4j bugzilla: https://bz.apache. > org/bugzilla/show_bug.cgi?id=50213, basically it is related to > synchronized doAppend() method in AppenderSkeleton class. > As far as I see the problem still appears in latest ops4j pax logging > version (1.10.1). > > Any suggestion how to fix or workaround this problem? > > Regards, > Andrei. > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: pax-logging alternative for java 9 jpms
The biggest problem with making pax-logging a JPMS module is making its dependencies all JPMS modules. Unless you can live with just the core logging plugins from log4j2 or logback (e.g., rolling file appender, stdout, etc.), that's not feasible yet. For example, if you're logging via JSON or XML, you'll need Jackson to be a module as well. Now I'm not sure if pax-logging has been updated to this yet, but the log4j2 implementation as of log4j 2.9.0 does have explicit Java 9 support for some things, and I'd imagine that logback isn't far behind. On 17 September 2017 at 13:32, Pavel <pavelkastor...@gmail.com> wrote: > Hi all > > I use pax-logging and know this product. Now I need something like for > Java 9 JPMS. > What I want is the following: > 1) support for all popular logging frameworks > 2) get log files by module name (as pax-logging does it for every bundle). > I mean I want > to have separate logging file for every module. > > Could anyone say if such product exists? > > If I don't find existing product I want to take pax-logging (two > subprojects: > pax-logging-api and pax-logging-service) and modify them for JPMS - > under apache license 2.0. Is such project interesting for OPS4J community? > > Best regards, Pavel > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: CDI?
I'm not so sure about deprecated, but DS is the only dependency injection standard in OSGi that respects the dynamic nature of services. CDI, blueprint, etc., all have to rely on hacky proxies to emulate support while adding nonstandard extensions at times. On 7 August 2017 at 17:02, <r...@enjekt.org> wrote: > I posted this to the Karaf forum but it may more appropriately belong > here. It's going to be one or the other. > > Has CDI been deprecated from the OSGi specification. I was hoping to use > it in the future instead of Blueprint or DS or in addition to them. I re > all last year a new OSGi service export and reference annotations were > added. So this surprised me a bit. > > https://issues.apache.org/jira/browse/CAMEL-11029 > > According to that issue, Camel's CDI support for OSGi doesn't work because > CDI on OSGi is deprecated. > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [pax-logging] Is it OK to integrate BSD licensed bwaldvogel/log4j-systemd-journal-appender into pax logging?
One of the Flume appenders in Log4j2 requires BerkeleyDB which has a similar annoying license. Now I don't know of any licensing guidelines for ops4j specifically, but following the ASF's guidelines seems to make a lot of sense. On 28 July 2017 at 03:07, Stephen Kitt <st...@sk2.org> wrote: > Michael, > > (Re-sending from my subscribed address.) > > The canonical source of information regarding licence categories (A, B, and > X) from the ASF’s point of view is https://www.apache.org/legal/ > resolved.html > — that will answer similar questions for you in future. Note that licence > categorisation can evolve, see e.g. the JSON licence. > > Regards, > > Stephen > > > On Thu, 27 Jul 2017 19:27:00 +0200, Jean-Baptiste Onofré > <jeanbaptiste.ono...@gmail.com> wrote: > > > Hi > > > > BSD is a cat B but not cat X so yes it's possible. No worries. > > > > Regards > > JB > > > > On Jul 27, 2017, 19:16, at 19:16, Michael Vorburger <m...@vorburger.ch> > > wrote: > > >Hello Paxifians, > > > > > >For https://issues.apache.org/jira/browse/KARAF-5275 for > > >https://bugzilla.redhat.com/show_bug.cgi?id=1475951, a question: > > > > > >Would it be OK to bundle the BSD licensed > > >https://github.com/bwaldvogel/ > > >log4j-systemd-journal-appender into OPS4j Pax Logging? > > > > > >I'm willing to put together a pull request proposing this, but wanted > > >to > > >first double check before with you guys if anyone here had any > > >reservations > > >on the license side... is embedding a BSD licensed library into a ASL > > >licensed project cool? > > > > > >Tx, > > >M. > > >___ > > >Michael Vorburger > > >http://www.vorburger.ch > > > > > >-- > > >-- > > >-- > > >OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > > > > >--- > > >You received this message because you are subscribed to the Google > > >Groups "OPS4J" group. > > >To unsubscribe from this group and stop receiving emails from it, send > > >an email to ops4j+unsubscr...@googlegroups.com. > > >For more options, visit https://groups.google.com/d/optout. > > > > -- > > -- > > -- > > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > > > --- > > You received this message because you are subscribed to the Google Groups > > "OPS4J" group. To unsubscribe from this group and stop receiving emails > > from it, send an email to ops4j+unsubscr...@googlegroups.com. For more > > options, visit https://groups.google.com/d/optout. > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [DISCUSS] Release Pax-Logging 1.10.0
The release should be available now. I'll be making a release announcement within the next few hours. On 3 April 2017 at 09:53, Guillaume Nodet <gno...@apache.org> wrote: > Sure, np. > Please ping me when the release is available and I'll do the upgrade and > release. > > 2017-04-03 16:12 GMT+02:00 Matt Sicker <boa...@gmail.com>: > >> I just started a release for Log4j 2.8.2 yesterday. Could you wait for >> that before cutting a release? Should be done by Wednesday. >> >> On 3 April 2017 at 04:45, Jean-Baptiste Onofré < >> jeanbaptiste.ono...@gmail.com> wrote: >> >>> +1 >>> >>> No problem from my side. >>> Thanks ! >>> >>> Regards >>> JB >>> >>> On 04/03/2017 11:36 AM, Guillaume Nodet wrote: >>> >>> I'd like to start releasing pax-logging 1.10.0. >>> Anything needed before I cut the release ? >>> >>> Cheers, >>> Guillaume >>> >>> -- >>> -- >>> -- >>> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OPS4J" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to ops4j+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> -- >>> -- >>> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "OPS4J" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to ops4j+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Matt Sicker <boa...@gmail.com> >> >> -- >> -- >> -- >> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OPS4J" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ops4j+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > Guillaume Nodet > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Rather big list of dependencies for Pax Logging Log4j2
Without those imports, wouldn't that mean none of those features could work? On 3 April 2017 at 10:40, 'Achim Nierbeck' via OPS4J <ops4j@googlegroups.com > wrote: > Hi, > > I'm not sure we had this amount of optional dependencies in the "old" Pax > Logging service, but > right now I'm unsure if we really want this list of Imports in the log4j > service bundle: > > Import-Package = > com.fasterxml.jackson.annotation;resolution:=optional, > com.fasterxml.jackson.core;resolution:=optional, > com.fasterxml.jackson.core.io;resolution:=optional, > com.fasterxml.jackson.core.type;resolution:=optional, > com.fasterxml.jackson.core.util;resolution:=optional, > com.fasterxml.jackson.databind;resolution:=optional, > com.fasterxml.jackson.databind.annotation;resolution:=optional, > com.fasterxml.jackson.databind.deser.std;resolution:=optional, > com.fasterxml.jackson.databind.module;resolution:=optional, > com.fasterxml.jackson.databind.node;resolution:=optional, > com.fasterxml.jackson.databind.ser;resolution:=optional, > com.fasterxml.jackson.databind.ser.impl;resolution:=optional, > com.fasterxml.jackson.databind.ser.std;resolution:=optional, > com.fasterxml.jackson.dataformat.xml;resolution:=optional, > com.fasterxml.jackson.dataformat.xml.annotation;resolution:=optional, > com.fasterxml.jackson.dataformat.xml.util;resolution:=optional, > com.fasterxml.jackson.dataformat.yaml;resolution:=optional, > com.lmax.disruptor;resolution:=optional, > com.lmax.disruptor.dsl;resolution:=optional, > javax.activation;resolution:=optional, > javax.annotation.processing;resolution:=optional, > javax.crypto;resolution:=optional, > javax.jms;resolution:=optional, > javax.lang.model;resolution:=optional, > javax.lang.model.element;resolution:=optional, > javax.lang.model.util;resolution:=optional, > javax.mail;resolution:=optional, > javax.mail.internet;resolution:=optional, > javax.mail.util;resolution:=optional, > javax.management;resolution:=optional, > javax.naming;resolution:=optional, > javax.net;resolution:=optional, > javax.net.ssl;resolution:=optional, > javax.persistence;resolution:=optional, > javax.script;resolution:=optional, > javax.sql;resolution:=optional, > javax.tools;resolution:=optional, > javax.xml.bind, > javax.xml.parsers, > javax.xml.stream, > javax.xml.transform, > javax.xml.transform.stream, > javax.xml.validation, > org.apache.commons.compress.compressors;resolution:=optional, > org.apache.commons.compress.utils;resolution:=optional, > org.apache.commons.csv;resolution:=optional, > org.apache.kafka.clients.producer;resolution:=optional, > org.codehaus.stax2;resolution:=optional, > org.knopflerfish.service.log;provider=paxlogging;version="[1.1.0,2.0.0)", > org.ops4j.pax.logging;version="[0.9.5,2.0.0)", > org.ops4j.pax.logging.spi;version="[0.9.5,2.0.0)", > org.osgi.framework;version="[1.0.0,2.0.0)", > org.osgi.framework.wiring;version="[1.0,2)", > org.osgi.service.cm;version="[1.0.0,2.0.0)", > org.osgi.service.event;resolution:=optional;version="[1.0.0,2.0.0)", > org.osgi.service.log;version="[1.3.0,2.0.0)", > org.osgi.util.tracker;version="[1.3.0,2.0.0)", > org.w3c.dom, > org.xml.sax, > org.zeromq;resolution:=optional > > > Especially since every time we have a new Optional dependency resolved > with Karaf will restart the gogo shell and tons of other bundles, just > because the logging service is refreshed ... > > Not to say it stalls any Pax-Exam test in case you try to test to install > a feature which > might provide one of those dependencies. > > regards, Achim > > > -- > > Apache Member > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> > > Software Architect / Project Manager / Scrum Master > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [pag-logging] Is it possible to completely turn off logging?
t;> Groups "OPS4J" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to ops4j+un...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> >>> Apache Member >>> Apache Karaf <http://karaf.apache.org/> Committer & PMC >>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer >>> & Project Lead >>> blog <http://notizblog.nierbeck.de/> >>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> >>> >>> Software Architect / Project Manager / Scrum Master >>> >>> -- >> -- >> -- >> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OPS4J" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ops4j+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > Apache Member > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> > > Software Architect / Project Manager / Scrum Master > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [pax-jdbc] Updating driver dependencies (since it's 2017)
Please go ahead and update as much as possible. I have a feeling things get out of date here only because nobody takes the initiative to keep dependencies up to date. On 23 March 2017 at 05:28, Holger Hoffstätte <hol...@applied-asynchrony.com> wrote: > Hello everyone! > > Achim just hijacked^h^h^h^h^hinvited me to ops4j and as first > task I just filed https://ops4j1.jira.com/browse/PAXJDBC-123 > which is about updating driver dependencies. > > We've been hit by some really bad bugs in the MariaDB driver, > which is seriously out of date. This is a problem since our > customized Karaf packaging installs boot features, and (so I > have been told) boot features can't be overridden. > > In any case it seems to me that many of the dependencies in > pax-jdb could use a refresh since it's 2017. So please add > your suggestions to the bug if you can vouch that a certain > version works reliably. I'll collect responses and bump > the dependencies for the next release. > > thanks, > Holger > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: PaxOsgi Appender
It's an appender plugin that lets you use your own implementation of PaxAppender (from pax-logging-api) OSGi services as an appender. Essentially, it's a way to write an appender that is abstract to pax-logging and not tied to any specific pax-logging implementation. On 1 November 2016 at 08:08, Nicolai Stäger <nicolaistae...@gmail.com> wrote: > Hi everyone, > we are using Karaf with Log4j2. But we are wondering, what the ...> appender does that is listed in many examples. I cannot find any > documentation on this. You can find it here in the example: > https://karaf.apache.org/manual/latest/#_log4j_v2_support > > Can anyone help me out, what this thing does? > Thanks a lot in advance! > > Best, > Nicolai > > -- > -- > -- > OPS4J - http://www.ops4j.org - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <boa...@gmail.com> -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
