It seems like it reimplements parts of Log4j's PatternLayout. On Wed, Jun 10, 2015 at 7:04 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
> Fair enough. Eventually, Log4j will be on Java 8 as well, but who knows > when that will be, Java 7 EOL or not. > > Gary > > On Tue, Jun 9, 2015 at 9:52 PM, Daniel Widdis <wid...@gmail.com> wrote: > > > I think this one is best left outside of the official log4j release for > > now. > > > > Its main dependency is Collabsoft's HipChatAPI ( > > https://bitbucket.org/collabsoft/hipchatapi/) which is still in "alpha" > > development (and signs are it's not being actively developed). That API > in > > turn is using version 1 of the HipChat API, which has now been deprecated > > with a note that "new development should use version 2". There is a > > project using the v2 HipChat API ( > https://github.com/evanwong/hipchat-java), > > but it has a Java 8 dependency. > > > > At some point when I get time I may fork my project and try to implement > > the new API... or better yet, fork the log4j project itself so a patch > will > > be easier. > > > > For now, a web search points to my project, a single-classfile Custom > > Appender implementation that's easy enough to add to any project. > > > > Dan > > > > > > On 6/9/15 9:09 PM, Gary Gregory wrote: > > > >> Oh, and FWIW, a JIRA and patch attached would be best. > >> > >> Gary > >> > >> On Tue, Jun 9, 2015 at 9:08 PM, Gary Gregory <garydgreg...@gmail.com> > >> wrote: > >> > >> I guess we have not considered this still. > >>> > >>> Thoughts from devs and users? > >>> > >>> Gary > >>> > >>> On Thu, Mar 12, 2015 at 1:05 AM, Daniel Widdis <wid...@gmail.com> > wrote: > >>> > >>> Works fine with 2.2. > >>>> > >>>> On 3/12/15 12:22 AM, Gary Gregory wrote: > >>>> > >>>> Note that 2.2 just came out. You might want to make sure your code > >>>>> still > >>>>> works with 2.2 and Git master. I'm not sure if anyone will have > cycles > >>>>> to > >>>>> look at this; I'm OOT for the next 4 days. > >>>>> > >>>>> Gary > >>>>> > >>>>> On Mon, Oct 20, 2014 at 6:32 AM, Gary Gregory < > garydgreg...@gmail.com> > >>>>> wrote: > >>>>> > >>>>> Dan, > >>>>> > >>>>>> We are in the middle of releasing Log4j 2.1. > >>>>>> > >>>>>> Once that is done, I think we'll be able to focus on new features. > >>>>>> > >>>>>> If all goes perfectly well, 2.1 will be out at the end of the week. > >>>>>> > >>>>>> Gary > >>>>>> > >>>>>> On Sun, Oct 19, 2014 at 3:00 PM, Daniel Widdis <wid...@gmail.com> > >>>>>> wrote: > >>>>>> > >>>>>> I've uploaded my project to github for the log4j2 community's > >>>>>> > >>>>>>> use/abuse. > >>>>>>> > >>>>>>> https://github.com/dbwiddis/log4j2-hipchat > >>>>>>> > >>>>>>> On 10/17/14, 12:18 PM, Daniel Widdis wrote: > >>>>>>> > >>>>>>> Threw something together. It works. Needs testing and more > >>>>>>> > >>>>>>>> javadocs, > >>>>>>>> of course... > >>>>>>>> > >>>>>>>> What's the best path to contribute? Just stick it up on a code > >>>>>>>> repository somewhere? Anyone want to collaborate? > >>>>>>>> > >>>>>>>> Dan > >>>>>>>> > >>>>>>>> On 10/17/14, 8:51 AM, Gary Gregory wrote: > >>>>>>>> > >>>>>>>> Patches welcome ;-) > >>>>>>>> > >>>>>>>>> Gary > >>>>>>>>> > >>>>>>>> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > > > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- [image: MagineTV] *Mikael Ståldal* Senior backend developer *Magine TV* mikael.stal...@magine.com Regeringsgatan 25 | 111 53 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
