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 <[email protected]> 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 - [email protected] > > --- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <[email protected]> -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
