logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <ggreg...@apache.org>
Subject Re: [ANN] Deleting receivers and components 'companions'
Date Wed, 05 Oct 2011 17:37:09 GMT
On Wed, Oct 5, 2011 at 1:30 PM, Christian Grobmeier <grobmeier@gmail.com>wrote:

> On Wed, Oct 5, 2011 at 7:25 PM, Gary Gregory <ggregory@apache.org> wrote:
> > This might help you get started (from Commons):
> > https://wiki.apache.org/commons/UsingNexus
>
> Thanks Gary, Actually I have helped editing this file. :-)
>
> But to be honest, I am not even sure if Nexus has been used before for
> log4j.  Well... lets see if Curt can comment, as he has done the past
> releases.
>

Check.

It's easy enough to ask infra to set up Nexus for a component through a
JIRA, I just did it for Commons IO and a while back for Commons Codec.

Gary


>
> Cheers
> Christian
>
> >
> > Gary
> >
> > On Wed, Oct 5, 2011 at 1:22 PM, Scott Deboy <scott.deboy@gmail.com>
> wrote:
> >>
> >> Yes a release ASAP would be great...
> >>
> >> I'd love to see a wiki page on how to release as well, with all the
> steps.
> >>
> >> Scott
> >>
> >> On Wed, Oct 5, 2011 at 10:16 AM, Christian Grobmeier <
> grobmeier@gmail.com>
> >> wrote:
> >>>
> >>> On Wed, Oct 5, 2011 at 6:47 PM, Scott Deboy <scott.deboy@gmail.com>
> >>> wrote:
> >>> > Well, rolling them in to core would be an option.  Curt had a
> rationale
> >>> > for
> >>> > companions, from a previous email:
> >>> >
> >>> > "The motivation to have "companions" as a distinct products was not
> to
> >>> > keep
> >>> > the log4j.jar trim, but allow the companions to be available for
> people
> >>> > who
> >>> > were stuck with older versions of log4j 1.2 (due to package managers
> or
> >>> > other software bundlers liking to distribution ancient versions of
> >>> > log4j
> >>> > 1.2)."
> >>> >
> >>> > I personally don't think support for receivers with older versions
of
> >>> > log4j
> >>> > is a big deal...so I would be ok with moving things in to core.
> >>>
> >>> +1
> >>>
> >>> In other terms, we should try to get a log4j release out pretty soon
> >>> to enable a chainsaw release, right?
> >>>
> >>> I cannot find a "how to release" page unfortunately. Maybe Curt can
> >>> comment if he can do / or can help with this task.
> >>>
> >>> Cheers
> >>> Christian
> >>>
> >>> >
> >>> > Scott
> >>> >
> >>> > On Wed, Oct 5, 2011 at 9:38 AM, Gary Gregory <ggregory@apache.org>
> >>> > wrote:
> >>> >>
> >>> >> On Wed, Oct 5, 2011 at 11: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
> >>> >>
> >>> >> I like (1), the fewer jars the better for me and the less chance
of
> >>> >> things
> >>> >> breaking in the future.
> >>> >>
> >>> >> Gayr
> >>> >>
> >>> >>>
> >>> >>> 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
> >>> >>>
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> 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
>
>


-- 
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://twitter.com/GaryGregory>

Mime
View raw message