On Wed, Oct 5, 2011 at 12:27 AM, Scott Deboy scott.de...@gmail.com wrote:
There are a number of people looking for resolution on the code signing cert
question (Eclipse plugins, maven artifacts, etc). I'll file a Jira issue.
Our case is relatively straightforward - hopefully infra can automate
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
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
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
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)..
Scott
On Wed, Oct 5, 2011 at 7:52 AM, Gary Gregory ggreg...@apache.org wrote:
Hi Christian,
We,
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
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).
Scott
On Wed, Oct 5, 2011 at 8:33 AM, Christian Grobmeier
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).
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
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
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
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
On Wed, Oct 5, 2011 at 11:33 AM, Christian Grobmeier grobme...@gmail.comwrote:
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
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
On Wed, Oct 5, 2011 at 6:47 PM, Scott Deboy scott.de...@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
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 grobme...@gmail.comwrote:
On Wed, Oct 5, 2011 at 6:47 PM, Scott Deboy scott.de...@gmail.com wrote:
Well, rolling them in
This might help you get started (from Commons):
https://wiki.apache.org/commons/UsingNexus
Gary
On Wed, Oct 5, 2011 at 1:22 PM, Scott Deboy scott.de...@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 7:25 PM, Gary Gregory ggreg...@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
On Wed, Oct 5, 2011 at 1:30 PM, Christian Grobmeier grobme...@gmail.comwrote:
On Wed, Oct 5, 2011 at 7:25 PM, Gary Gregory ggreg...@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
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
https://issues.apache.org/bugzilla/show_bug.cgi?id=50369
Gil Cottle gc...@redtown.org changed:
What|Removed |Added
CC||carn...@apache.org,
https://issues.apache.org/bugzilla/show_bug.cgi?id=50369
--- Comment #1 from Gil Cottle gc...@redtown.org 2011-10-05 19:22:15 UTC ---
Created attachment 27700
-- https://issues.apache.org/bugzilla/attachment.cgi?id=27700
Patch to fix comma issue
All that is missing is a '' and 'INFOcode'. I
https://issues.apache.org/bugzilla/show_bug.cgi?id=51361
--- Comment #1 from Gil Cottle gc...@redtown.org 2011-10-05 20:44:22 UTC ---
Created attachment 27701
-- https://issues.apache.org/bugzilla/attachment.cgi?id=27701
Patch for Misspelling
Made change request and added it to a patch
--
https://issues.apache.org/bugzilla/show_bug.cgi?id=51361
Gil Cottle gc...@redtown.org changed:
What|Removed |Added
CC||gc...@redtown.org
24 matches
Mail list logo
