logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: maven build for source does not work
Date Mon, 28 Apr 2014 23:49:06 GMT
Oh good point. We'll do security updates and such, but no more new features
or anything. It's in maintenance-only mode.


On 28 April 2014 18:46, Scott Deboy <scott.deboy@gmail.com> wrote:

> It is not true that we don't maintain 1.2 any longer. If important issues
> are found we may still address them even though we are focused on Log4j2.
> On Apr 28, 2014 4:01 PM, "Matt Sicker" <boards@gmail.com> wrote:
>
> > We don't maintain 1.2.x anymore. Also, I think you're supposed to use ant
> > to build 1.2.
> >
> > Please check out Log4j 2.0, though, as we're preparing to release that
> and
> > would like feedback.
> >
> >
> > On 28 April 2014 14:30, <Walter_Marvin@dellteam.com> wrote:
> >
> > > Dell - Internal Use - Confidential
> > >
> > >
> > > 1)      The pom file has to be updated to allow for maven-site-plugin
> 3.3
> > > rather than 3.1
> > >
> > > 2)      The mvm staging step gives a null pointer exception
> > >
> > > Apache.log4j-1.2.17
> > >
> > > Thanks
> > >
> > > Walter
> > >
> >
> >
> >
> > --
> > Matt Sicker <boards@gmail.com>
> >
>



-- 
Matt Sicker <boards@gmail.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message