To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4j-receivers has an issue affecting its community
Scott,
Curt had an interesting idea lately, he mentioned it might make sense
to move the companions code into chainsaw.
What do you think on that?
I like the idea - less releases, and no other interested parties in
having companions.
Please comment, when you can :-)
Cheers
Christian
At this point I'm only focusing only on 2.0. I've been wondering if I should
create a subproject for chainsaw or if it should remain separate. I already
moved a large part of extras in as a core part of the functionality.
Ralph
On Sep 1, 2011, at 4:13 AM, Christian Grobmeier wrote:
Scott,
On Thu, Sep 1, 2011 at 6:15 PM, Scott Deboy scott.de...@gmail.com wrote:
I think pulling in component would make sense...no one else probably uses
it. Receivers? I suppose if they were built as a separate jar that'd be
fine too, I have no idea who uses them if anyone.
We can always cut them
On Thu, Sep 1, 2011 at 4:09 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
At this point I'm only focusing only on 2.0. I've been wondering if I should
create a subproject for chainsaw or if it should remain separate. I already
moved a large part of extras in as a core part of the
On Sep 1, 2011, at 6:13 AM, Christian Grobmeier wrote:
Scott,
Curt had an interesting idea lately, he mentioned it might make sense
to move the companions code into chainsaw.
What do you think on that?
I like the idea - less releases, and no other interested parties in
having
