It probably should be done anyway, but the various components would also need to check for the presence of the disruptor and log a warning if it isn't there (I believe we do this for Jansi and Jackson) as the disruptor would have to be an optional dependency. In the async package it can be non-optional so this is less important for anyone using Maven.
Ralph On Apr 12, 2013, at 9:23 AM, Ralph Goers wrote: > Because it has a dependency on the Disruptor, which Remko has said may not > work on all JDKs > > Sent from my iPad > > On Apr 12, 2013, at 8:23 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > >> Why not more log4j-async into the core? >> >> Gary >> >> -- >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >> Java Persistence with Hibernate, Second Edition >> JUnit in Action, Second Edition >> Spring Batch in Action >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory
