Hi Mark These are only the glues, the deps all are set to provided. I think Gerhard suggested doing it that way, somilar to other Apache projects. The code is based on JUL only....
Romain Manni-Bucau <[email protected]> schrieb am Sa., 3. Jan. 2015 um 15:19: > Log4j 2 is not widely used and would be another dep - a pain in almost all > containers for sure - so im not to use it as api. > Le 3 janv. 2015 14:57, "Werner Keil" <[email protected]> a écrit : > > > Is there something wrong in using Log4J, especially V2 that has a decent > > separation of API and connectors similar fo SLF4J? > > > > Unless we wanted to minimize external dependencies, JUL is there not just > > since Java 8? > > > > Werner > > > > On Sat, Jan 3, 2015 at 2:40 PM, Mark Struberg <[email protected]> wrote: > > > > > Hi! > > > > > > I've seen we have plenty of logging frameworks in our core now. > > > I did already remove this once as I suggest to only use the > > > java.util.logging.Logger facade. > > > > > > Of course I'm aware that jul logger sucks. But we just use it as facade > > > really. There are plenty of frameworks to use this facade. > > > > > > I especially disklike slf4j in container projects because > > > a.) it often creates classloader issues > > > b.) there have been binary incompatible changes in the past. That might > > > create NoClassDefFound and other bad situations within customer > project. > > > > > > So I suggest we really go back to jul only. > > > > > > > > > LieGrue, > > > strub > > > > > >
