logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Deboy <scott.de...@gmail.com>
Subject Re: [ANN] Deleting receivers and components 'companions'
Date Wed, 05 Oct 2011 15:54:03 GMT
Yeah, sort of like what happened to zeroconf...

I think Component could go back in to core.

Scott


On Wed, Oct 5, 2011 at 8:46 AM, Christian Grobmeier <grobmeier@gmail.com>wrote:

> On Wed, Oct 5, 2011 at 5:44 PM, Scott Deboy <scott.deboy@gmail.com> wrote:
> > Here's my preference:
> >
> > I would expect more receivers will be added in the future, or there may
> be
> > bugs we want to fix..so I would leave receivers and extras as companions
> and
> > move component somewhere (Chainsaw or core).
>
> OK, and receivers and extras website will stay as it is now?
> Only "component" will be removed?
>
> Christian
>
> >
> > Scott
> >
> > On Wed, Oct 5, 2011 at 8:33 AM, Christian Grobmeier <grobmeier@gmail.com
> >
> > wrote:
> >>
> >> Gary, thanks for explaining your situation
> >>
> >> On Wed, Oct 5, 2011 at 4:57 PM, Scott Deboy <scott.deboy@gmail.com>
> wrote:
> >> > We could leave receivers as their own companion...component is so
> small
> >> > it
> >> > should either go back in to core or into Chainsaw (there are some
> >> > repositoryselector extensions that are useful, etc)..
> >>
> >> another solution is to make some kind of "logging attic" and leave the
> >> code there, unmaintained.
> >> Or we do only remove the website as planned and leave the code were it
> is.
> >>
> >> So we have now:
> >>
> >> 1) move receivers code to log4j-core
> >> 2) move receivers code to Chainsaw
> >> 3) move receivers code to logging-attic, from which anybody who wants
> >> can copy it
> >> 4) leave code were it is, just delete the reference from the website.
> >> Users who are in need still now were it is or know how to lookup
> >>
> >> For the sake of pragmatism I would prefer #3
> >>
> >> cheers,
> >> Christian
> >>
> >> >
> >> > Scott
> >> >
> >> > On Wed, Oct 5, 2011 at 7:52 AM, Gary Gregory <ggregory@apache.org>
> >> > wrote:
> >> >>
> >> >> Hi Christian,
> >> >>
> >> >> We, at Seagull Software, a division of Rocket Software, use the jars
> in
> >> >> our LegaSuite app server [1] and some tools.
> >> >>
> >> >> Moving the code would be an impediment to updating to the next
> release
> >> >> of
> >> >> the jars.
> >> >>
> >> >> Gary
> >> >>
> >> >> [1]
> >> >> http://seagull.rocketsoftware.com/products/application-modernization
> >> >>
> >> >> On Wed, Oct 5, 2011 at 10:28 AM, Christian Grobmeier
> >> >> <grobmeier@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> On Tue, Oct 4, 2011 at 9:44 PM, Gary Gregory <ggregory@apache.org>
> >> >>> wrote:
> >> >>> > We use the XMLSocketReceiver.
> >> >>>
> >> >>> Who actually is "we"?
> >> >>> Can you copy it over? Or do you need it were it is?
> >> >>>
> >> >>> Cheers
> >> >>> Christian
> >> >>>
> >> >>>
> >> >>> >
> >> >>> > Gary
> >> >>> >
> >> >>> > On Tue, Oct 4, 2011 at 1:41 PM, Scott Deboy <
> scott.deboy@gmail.com>
> >> >>> > wrote:
> >> >>> >>
> >> >>> >> The sources for the unreleased receivers and components
> companions
> >> >>> >> have
> >> >>> >> been copied in to the Chainsaw source tree, based on the
> assumption
> >> >>> >> that
> >> >>> >> they are only useful to Chainsaw.  Unless there are any
> objections,
> >> >>> >> I
> >> >>> >> plan
> >> >>> >> on deleting the component and receivers companions from
> subversion,
> >> >>> >> with
> >> >>> >> corresponding changes to the site made shortly after to
remove
> them
> >> >>> >> from the
> >> >>> >> website.
> >> >>> >>
> >> >>> >> The sources were copied unchanged, so if anyone needs
access to a
> >> >>> >> receiver, they are still accessible, they would just need
to be
> >> >>> >> copied
> >> >>> >> out
> >> >>> >> of the Chainsaw source tree.
> >> >>> >>
> >> >>> >> When the website changes are made, the 'companion's link
will be
> >> >>> >> removed
> >> >>> >> and replaced with the only remaining standalone 'companion':
> >> >>> >> extras.
> >> >>> >>
> >> >>> >> Let me know if you have any objections.
> >> >>> >>
> >> >>> >> Thanks
> >> >>> >>
> >> >>> >> Scott
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > --
> >> >>> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> >> >>> > JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> >> >>> > Spring Batch in Action: http://bit.ly/bqpbCK
> >> >>> > Blog: http://garygregory.wordpress.com
> >> >>> > Home: http://garygregory.com/
> >> >>> > Tweet! http://twitter.com/GaryGregory
> >> >>> >
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> http://www.grobmeier.de
> >> >>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> >> >> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> >> >> Spring Batch in Action: http://bit.ly/bqpbCK
> >> >> Blog: http://garygregory.wordpress.com
> >> >> Home: http://garygregory.com/
> >> >> Tweet! http://twitter.com/GaryGregory
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> http://www.grobmeier.de
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >>
> >
> >
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>

Mime
View raw message