You can use 2.0. We're all working on that.

On 29 April 2014 08:53, <walter_mar...@dellteam.com> wrote:

> Dell - Internal Use - Confidential
> I would if I could, but I can't so I shan't...
>
> -----Original Message-----
> From: Remko Popma [mailto:remko.po...@gmail.com]
> Sent: Tuesday, April 29, 2014 8:32 AM
> To: Log4J Users List
> Subject: Re: maven build for source does not work
>
> Walter,
>
> It's open source though. Nothing stops you from helping out.
>
> Best regards,
> Remko
>
> Sent from my iPhone
>
> > On 2014/04/29, at 22:24, wrote:
> >
> > Dell - Internal Use - Confidential
> > What? No maintenance on the latest released source?
> >
> > -----Original Message-----
> > From: Scott Deboy [mailto:scott.de...@gmail.com]
> > Sent: Monday, April 28, 2014 6:46 PM
> > To: Log4J Users List
> > Subject: Re: maven build for source does not work
> >
> > 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" 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, 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
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>



-- 
Matt Sicker <boa...@gmail.com>

Reply via email to