You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Paul Smith <ps...@aconex.com> on 2005/02/23 22:18:43 UTC
[VOTE]: Chainsaw as seperate module
This is a formalization of the thread 'Chainsaw as seperate CVS module'.
1. Propose to move out Chainsaw sources into it's own CVS module,
'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 build.
2. Propose to make the new 'logging-chainsaw' as CVS module, and not use
SVN until the entire Logging Service community is ready for SVN migration.
3. Propose to defer the decision on whether Chainsaw (or Logging Gui's?)
is made a seperate sub-project until after establishing a cleanly
seperated CVS/build environment is in operation.
4. Propose that all existing log4j committers still have full access to
this new module.
+1 [ ] Make it so
0 [ ] *yawn*
-1 [ ] Leave Chainsaw where it is
cheers,
Paul Smith
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Ceki Gülcü <ce...@qos.ch>.
+1
OK, then I'll go create the 'logging-chainsaw' CVS module and grant the
appropritate karma on the Apache Server.
At 10:18 PM 2/23/2005, Paul Smith wrote:
>This is a formalization of the thread 'Chainsaw as seperate CVS module'.
>
>1. Propose to move out Chainsaw sources into it's own CVS module,
>'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 build.
>
>2. Propose to make the new 'logging-chainsaw' as CVS module, and not use
>SVN until the entire Logging Service community is ready for SVN migration.
>
>3. Propose to defer the decision on whether Chainsaw (or Logging Gui's?)
>is made a seperate sub-project until after establishing a cleanly
>seperated CVS/build environment is in operation.
>
>4. Propose that all existing log4j committers still have full access to
>this new module.
>
>+1 [ ] Make it so
>0 [ ] *yawn* -1 [ ] Leave Chainsaw where it is
>cheers,
>
>Paul Smith
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Jacob Kjome <ho...@visi.com>.
+1
Jake
Quoting Paul Smith <ps...@aconex.com>:
> This is a formalization of the thread 'Chainsaw as seperate CVS module'.
>
> 1. Propose to move out Chainsaw sources into it's own CVS module,
> 'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 build.
>
> 2. Propose to make the new 'logging-chainsaw' as CVS module, and not use
> SVN until the entire Logging Service community is ready for SVN migration.
>
> 3. Propose to defer the decision on whether Chainsaw (or Logging Gui's?)
> is made a seperate sub-project until after establishing a cleanly
> seperated CVS/build environment is in operation.
>
> 4. Propose that all existing log4j committers still have full access to
> this new module.
>
> +1 [ ] Make it so
> 0 [ ] *yawn*
> -1 [ ] Leave Chainsaw where it is
>
> cheers,
>
> Paul Smith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Johan Känngård <jo...@kanngard.net>.
+1
_______________________
Johan Känngård
johan@kanngard.net
http://dev.kanngard.net
Paul Smith wrote:
> This is a formalization of the thread 'Chainsaw as seperate CVS module'.
>
> 1. Propose to move out Chainsaw sources into it's own CVS module,
> 'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 build.
>
> 2. Propose to make the new 'logging-chainsaw' as CVS module, and not
> use SVN until the entire Logging Service community is ready for SVN
> migration.
>
> 3. Propose to defer the decision on whether Chainsaw (or Logging
> Gui's?) is made a seperate sub-project until after establishing a
> cleanly seperated CVS/build environment is in operation.
>
> 4. Propose that all existing log4j committers still have full access
> to this new module.
>
> +1 [ ] Make it so
> 0 [ ] *yawn* -1 [ ] Leave Chainsaw where it is
> cheers,
>
> Paul Smith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Paul Smith <ps...@aconex.com>.
As part of the preparations for this move I have tagged the HEAD of
logging-log4j as so:
cvs rtag TAG_CHAINSAW2_MOVE logging-log4j
cheers,
Paul
Paul Smith wrote:
> Thanks Ceki for doing this.
>
> I was in the last phase of preparing the module when Ceki reminded me
> that we can copy the CVS history over if we do some funky CVS tricks.
> My local repository had just copied the files. We would have had the
> history in the logging-log4j module, but not in logging-chainsaw
> module, and I agree with Ceki that the history is worth keeping together.
>
> So, it's just going to take a touch longer than I thought to get this
> together. Scott, if you have any changes, could you bundle them as
> patches and fire them over to me?
>
> I have also modified the log4j build process to clean out any Chainsaw
> related stuff to keep log4j nice and clean, I'll submit that at the
> same time when I feel it's ready to roll.
>
> One silly thing I just realised was that I had not tested the log4j
> unit tests BEFORE making the change, just to make sure they all
> succeed. I assume that they still do... ? I just want to make sure
> that if they don't work it's because of my changes, and not because of
> an existing problem. If someone could confirm everything's a-ok, that
> would be great.
>
> I'll try and get this sorted out today, but not sure how that will go
> with what else I have on at work.
>
> cheers,
>
> Paul
>
> Ceki Gülcü wrote:
>
>> At 06:36 AM 2/24/2005, Paul Smith wrote:
>>
>>> ok, only Ceki's vote to go, and I understand he's still recovering
>>> from some hardware problems. In a recent mail, Ceki intimated he
>>> was, in principle, in favour, so I will _begin_ this process
>>> locally, but not commit, and wait until Ceki has a chance to cast
>>> his vote.
>>
>>
>>
>> The CVS module 'logging-chainsaw' has been created, appropriate karma
>> granted.
>>
>> I'll send a message to general@logging.apache.org to inform the rest
>> of Logging Services.
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Paul Smith <ps...@aconex.com>.
Thanks Ceki for doing this.
I was in the last phase of preparing the module when Ceki reminded me
that we can copy the CVS history over if we do some funky CVS tricks.
My local repository had just copied the files. We would have had the
history in the logging-log4j module, but not in logging-chainsaw module,
and I agree with Ceki that the history is worth keeping together.
So, it's just going to take a touch longer than I thought to get this
together. Scott, if you have any changes, could you bundle them as
patches and fire them over to me?
I have also modified the log4j build process to clean out any Chainsaw
related stuff to keep log4j nice and clean, I'll submit that at the same
time when I feel it's ready to roll.
One silly thing I just realised was that I had not tested the log4j unit
tests BEFORE making the change, just to make sure they all succeed. I
assume that they still do... ? I just want to make sure that if they
don't work it's because of my changes, and not because of an existing
problem. If someone could confirm everything's a-ok, that would be great.
I'll try and get this sorted out today, but not sure how that will go
with what else I have on at work.
cheers,
Paul
Ceki Gülcü wrote:
> At 06:36 AM 2/24/2005, Paul Smith wrote:
>
>> ok, only Ceki's vote to go, and I understand he's still recovering
>> from some hardware problems. In a recent mail, Ceki intimated he
>> was, in principle, in favour, so I will _begin_ this process
>> locally, but not commit, and wait until Ceki has a chance to cast his
>> vote.
>
>
> The CVS module 'logging-chainsaw' has been created, appropriate karma
> granted.
>
> I'll send a message to general@logging.apache.org to inform the rest
> of Logging Services.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Ceki Gülcü <ce...@qos.ch>.
At 06:36 AM 2/24/2005, Paul Smith wrote:
>ok, only Ceki's vote to go, and I understand he's still recovering from
>some hardware problems. In a recent mail, Ceki intimated he was, in
>principle, in favour, so I will _begin_ this process locally, but not
>commit, and wait until Ceki has a chance to cast his vote.
The CVS module 'logging-chainsaw' has been created, appropriate karma granted.
I'll send a message to general@logging.apache.org to inform the rest of
Logging Services.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Paul Smith <ps...@aconex.com>.
ok, only Ceki's vote to go, and I understand he's still recovering from
some hardware problems. In a recent mail, Ceki intimated he was, in
principle, in favour, so I will _begin_ this process locally, but not
commit, and wait until Ceki has a chance to cast his vote.
cheers,
Paul Smith
Paul Smith wrote:
> This is a formalization of the thread 'Chainsaw as seperate CVS module'.
>
> 1. Propose to move out Chainsaw sources into it's own CVS module,
> 'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 build.
>
> 2. Propose to make the new 'logging-chainsaw' as CVS module, and not
> use SVN until the entire Logging Service community is ready for SVN
> migration.
>
> 3. Propose to defer the decision on whether Chainsaw (or Logging
> Gui's?) is made a seperate sub-project until after establishing a
> cleanly seperated CVS/build environment is in operation.
>
> 4. Propose that all existing log4j committers still have full access
> to this new module.
>
> +1 [ ] Make it so
> 0 [ ] *yawn* -1 [ ] Leave Chainsaw where it is
> cheers,
>
> Paul Smith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: [VOTE]: Chainsaw as seperate module
Posted by Yoav Shapira <yo...@MIT.EDU>.
+1 from me as well ;)
Yoav
> -----Original Message-----
> From: Paul Smith [mailto:psmith@aconex.com]
> Sent: Wednesday, February 23, 2005 4:19 PM
> To: log4j-dev@logging.apache.org
> Subject: [VOTE]: Chainsaw as seperate module
>
> This is a formalization of the thread 'Chainsaw as seperate CVS module'.
>
> 1. Propose to move out Chainsaw sources into it's own CVS module,
> 'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 build.
>
> 2. Propose to make the new 'logging-chainsaw' as CVS module, and not use
> SVN until the entire Logging Service community is ready for SVN migration.
>
> 3. Propose to defer the decision on whether Chainsaw (or Logging Gui's?)
> is made a seperate sub-project until after establishing a cleanly
> seperated CVS/build environment is in operation.
>
> 4. Propose that all existing log4j committers still have full access to
> this new module.
>
> +1 [ ] Make it so
> 0 [ ] *yawn*
> -1 [ ] Leave Chainsaw where it is
>
> cheers,
>
> Paul Smith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE]: Chainsaw as seperate module
Posted by Curt Arnold <ca...@apache.org>.
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: [VOTE]: Chainsaw as seperate module
Posted by Mark Womack <wo...@adobe.com>.
+1 Engage!
> -----Original Message-----
> From: Paul Smith [mailto:psmith@aconex.com]
> Sent: Wednesday, February 23, 2005 1:19 PM
> To: log4j-dev@logging.apache.org
> Subject: [VOTE]: Chainsaw as seperate module
>
> This is a formalization of the thread 'Chainsaw as seperate CVS module'.
>
> 1. Propose to move out Chainsaw sources into it's own CVS module,
> 'logging-chainsaw'. Chainsaw will rely on a log4j 1.3 build.
>
> 2. Propose to make the new 'logging-chainsaw' as CVS module, and not use
> SVN until the entire Logging Service community is ready for SVN migration.
>
> 3. Propose to defer the decision on whether Chainsaw (or Logging Gui's?)
> is made a seperate sub-project until after establishing a cleanly
> seperated CVS/build environment is in operation.
>
> 4. Propose that all existing log4j committers still have full access to
> this new module.
>
> +1 [ ] Make it so
> 0 [ ] *yawn*
> -1 [ ] Leave Chainsaw where it is
>
> cheers,
>
> Paul Smith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org