You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Wa...@DellTeam.com on 2014/04/28 21:30:44 UTC

maven build for source does not work

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

Re: maven build for source does not work

Posted by Matt Sicker <bo...@gmail.com>.
Just FYI, I was able to get 1.2.17 to build. If you're on Mac OS X, make
sure to build it with the Java 1.6 that comes with Mac OS X.


On 29 April 2014 09:11, Matt Sicker <bo...@gmail.com> wrote:

> You can use 2.0. We're all working on that.
>
>
> On 29 April 2014 08:53, <Wa...@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 <bo...@gmail.com>
>



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

Re: maven build for source does not work

Posted by Matt Sicker <bo...@gmail.com>.
You can use 2.0. We're all working on that.


On 29 April 2014 08:53, <Wa...@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 <bo...@gmail.com>

RE: maven build for source does not work

Posted by Wa...@DellTeam.com.
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

Re: maven build for source does not work

Posted by Remko Popma <re...@gmail.com>.
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, <Wa...@DellTeam.com> 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


RE: maven build for source does not work

Posted by Wa...@DellTeam.com.
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
>

Re: maven build for source does not work

Posted by Matt Sicker <bo...@gmail.com>.
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 <sc...@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" <bo...@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, <Wa...@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 <bo...@gmail.com>
> >
>



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

Re: maven build for source does not work

Posted by Scott Deboy <sc...@gmail.com>.
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" <bo...@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, <Wa...@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 <bo...@gmail.com>
>

RE: maven build for source does not work

Posted by Wa...@DellTeam.com.
Dell - Internal Use - Confidential
What no maintenance on the latest RELEASED source?

-----Original Message-----
From: Matt Sicker [mailto:boards@gmail.com]
Sent: Monday, April 28, 2014 6:01 PM
To: Log4J Users List
Subject: Re: maven build for source does not work

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

Re: maven build for source does not work

Posted by Matt Sicker <bo...@gmail.com>.
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, <Wa...@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 <bo...@gmail.com>