I had copied all the code in to Chainsaw, but it didn't seem like it would make sense to have it in both Receivers and Chainsaw.
I think pulling everything in to Extras would work..Extras are mostly appender-side things (LogSF, Filters, PatternConverters, Rolling and TriggeringPolicy), but it is sort of a dumping ground for everything that isn't core. Scott On Wed, Oct 5, 2011 at 9:12 AM, Christian Grobmeier <grobme...@gmail.com>wrote: > On Wed, Oct 5, 2011 at 6:09 PM, Scott Deboy <scott.de...@gmail.com> wrote: > > Of course, receivers has not yet had an official release, and since > > receivers depends on the component code, we need a release of wherever > that > > goes first. > > > > Which means component can't go into chainsaw because of the > dependencies.. > > > > So to get Chainsaw out the door, we first have to move component code to > > core and release a log4j with that code, then release receivers and then > > we'll be able to get Chainsaw out. > > > > Think it's possible to get a log4j core release out shortly with > component > > included? If not, I suppose moving component in to Receiver would make > more > > sense. > > Oh... i missed that somehow. I had the impression you have already > copied all code you need to Chainsaw and you are able to release > > Is it possible to move receiver, component and extras into one > component and release that? > > > > > > > Scott > > > > On Wed, Oct 5, 2011 at 8:56 AM, Christian Grobmeier <grobme...@gmail.com > > > > wrote: > >> > >> On Wed, Oct 5, 2011 at 5:54 PM, Scott Deboy <scott.de...@gmail.com> > wrote: > >> > Yeah, sort of like what happened to zeroconf... > >> > > >> > I think Component could go back in to core. > >> > >> OK.. then lets wait for another couple of hours, maybe other people > >> want to stand up. Afterwards I will remove the component website, but > >> leave reiceivers and extras website were it is now. > >> > >> > > >> > Scott > >> > > >> > > >> > On Wed, Oct 5, 2011 at 8:46 AM, Christian Grobmeier > >> > <grobme...@gmail.com> > >> > wrote: > >> >> > >> >> On Wed, Oct 5, 2011 at 5:44 PM, Scott Deboy <scott.de...@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 > >> >> > <grobme...@gmail.com> > >> >> > wrote: > >> >> >> > >> >> >> Gary, thanks for explaining your situation > >> >> >> > >> >> >> On Wed, Oct 5, 2011 at 4:57 PM, Scott Deboy < > scott.de...@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 < > ggreg...@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 > >> >> >> >> <grobme...@gmail.com> > >> >> >> >> wrote: > >> >> >> >>> > >> >> >> >>> On Tue, Oct 4, 2011 at 9:44 PM, Gary Gregory > >> >> >> >>> <ggreg...@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.de...@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: garydgreg...@gmail.com | ggreg...@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-unsubscr...@logging.apache.org > >> >> >> >>> For additional commands, e-mail: > >> >> >> >>> log4j-dev-h...@logging.apache.org > >> >> >> >>> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> -- > >> >> >> >> E-Mail: garydgreg...@gmail.com | ggreg...@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-unsubscr...@logging.apache.org > >> >> >> For additional commands, e-mail: > log4j-dev-h...@logging.apache.org > >> >> >> > >> >> > > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> http://www.grobmeier.de > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > >> >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org > >> >> > >> > > >> > > >> > >> > >> > >> -- > >> http://www.grobmeier.de > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org > >> > > > > > > > > -- > http://www.grobmeier.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > >
