Hi Ray,
That’s interesting. Thanks for sharing. I think your point of view makes sense: > Logging is an infrastructure detail unlike any other. It really must be > bootstrapped with the runtime as early as possible I still don’t like having to pull in dependencies, though. Doing a quick google “java logging 2018” gave me this article: https://stackify.com/logging-java/ I think the conclusion is correct: > The state of logging in Java is a big mess: it’s very fragmented between a > small number of frameworks. Would be great to solve this problem using pure OSGi… I wouldn’t mind if the backend implementation were used as an embedded library without adding to the number of dependencies. Do you think it would be difficult to change the build configuration to make this happen? If the fix is simple, I could make my own fork. Or maybe Felix could provide both options, depending if people want to minimize their code base or minimize dependencies. Personally, I prefer the latter. wdyt? Cheers, =David _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
