[ https://issues.jboss.org/browse/JBLOGGING-118?page=com.atlassian.jira.plu... ] Murmur Murmur edited comment on JBLOGGING-118 at 10/5/15 7:29 AM: ------------------------------------------------------------------ I don't have a luxury of installing new jars server-side. All war files should be self contained applications. Some apps use a standard JDK provided logging capability, want to minimize all extra libraries or both valid reasons. This is currently a no-go if app is using say OpenJPA+JerseyRest+validator@annotations, jboss-logging is not behaving nice with any of that combination. Is there an internal valid reasons to have a subclass of Level even if it's known to create memory problems? If yes I understand this and won't push this change anymore. I use my own version of library and state in Stackoverflow and rest forums it is just an unofficial fix, don't expect it to pull regular upstream changes. Another globally side-effect safe working solution, very easy to implement would be to have JDKLoggerProvider2.java+JDKLogger2.java implementation. It did not use JDKLevel.java class at all. No fragmented jboss-logging libraries in wild. was (Author: murmur001): I don't have a luxury of installing new jars server-side. All war files should be self contained applications. Some apps use a standard JDK provided logging capability, want to minimize all extra libraries or both valid reasons. This is currently a no-go if app is using say OpenJPA+JerseyRest+validator@annotations, jboss-logging is not behaving nice with any of that combination. Is there an internal valid reasons to have a subclass of Level even if it's known to create memory problems? If yes I understand this and and won't push this change anymore. I use my own version of library and state in Stackoverflow and rest forums it is just an unofficial fix, don't expect it to pull regular upstream changes. Another globally side-effect safe working solution, very easy to implement would be to have JDKLoggerProvider2.java+JDKLogger2.java implementation. It did not use JDKLevel.java class at all. No fragmented jboss-logging libraries in wild. -- This message was sent by Atlassian JIRA (v6.4.11#64026)