Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: pass (nike.apache.org: domain of boards@gmail.com designates
 209.85.214.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <C4A4624C5EA472408D8E89555D0E6E52C277E5@DFWX10HMPTC01.AMER.DELL.COM>
References: 
 <C4A4624C5EA472408D8E89555D0E6E52C272FC@DFWX10HMPTC01.AMER.DELL.COM>
	<CACmp6kqgE+Z1zYZgKxaQxTukbc7-j2QpUv-n=Cr_uFo3jhJR9g@mail.gmail.com>
	<CADBq88DGO21n_Wk3bvPg04dvBcZA2zL9M1n5WD1LzyiR2ewnag@mail.gmail.com>
	<C4A4624C5EA472408D8E89555D0E6E52C277BB@DFWX10HMPTC01.AMER.DELL.COM>
	<A84D2A02-26F0-46AF-9AFD-9F2C481B1082@gmail.com>
	<C4A4624C5EA472408D8E89555D0E6E52C277E5@DFWX10HMPTC01.AMER.DELL.COM>
Date: Tue, 29 Apr 2014 09:11:54 -0500
Message-ID: 
 <CACmp6kqpdEnQVs9KLoBywrx3ynoOLuSvHfqFsfy=5X7Y8qf8RQ@mail.gmail.com>
Subject: Re: maven build for source does not work
From: Matt Sicker <boards@gmail.com>
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2a20c985b8104f82f0306

--001a11c2a20c985b8104f82f0306
Content-Type: text/plain; charset=UTF-8

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


On 29 April 2014 08:53, <Walter_Marvin@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.popma@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.deboy@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-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>


-- 
Matt Sicker <boards@gmail.com>

--001a11c2a20c985b8104f82f0306--