I continue to tweak it occasionally, not much lately. Not updating release
because I never got around to branding.
The dmg is for x86 but I've been updating snapshots on people.
It has a lot of good features now but has warts (timestamp parsing slowness
mostly).
I will continue to tweak it but
+1
On Jul 11, 2015 8:29 AM, Ralph Goers ralph.go...@dslextreme.com wrote:
+1
Ralph
On Jul 11, 2015, at 7:15 AM, Christian Grobmeier grobme...@apache.org
wrote:
Hello all,
as previously discussed, this is a vote to label Log4j 1.x as EOL.
This means:
1. label Log4j 1.x as
Yes - infra finally finished this!
I've already filed a jira. https://issues.apache.org/jira/browse/INFRA-8439
Maybe we will finally get this out the door.
Scott
Scott
On Oct 16, 2014 5:11 AM, Christian Grobmeier grobme...@gmail.com wrote:
Hi all,
specifically this is a question to Scott:
FYI, I filed https://issues.apache.org/jira/browse/INFRA-8439 -
Logging Services Chainsaw code signing support
Scott
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail:
Chainsaw is actually the immediate need for the code signing cert.
Scott
On Aug 29, 2014 9:19 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
Why can’t it be used to sign release artifacts?
Ralph
On Aug 29, 2014, at 7:55 PM, Matt Sicker boa...@gmail.com wrote:
Oh that's definitely a
+1
On Aug 5, 2014 7:18 AM, Matt Sicker boa...@gmail.com wrote:
This topic was brought up elsewhere, so I'd like to propose a vote on
switching to Git.
+1 for me
--
Matt Sicker boa...@gmail.com
+1
On 6/26/14, Gary Gregory garydgreg...@gmail.com wrote:
Or you could not run tests in parallel and keep it simple. This is not a
problem that needs solving and make the code harder to understand and
maintain.
Gary
On Thu, Jun 26, 2014 at 4:50 PM, Matt Sicker boa...@gmail.com wrote:
A
+1
On Jun 15, 2014 4:05 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
Do we need the builders? As I said, I prefer only one way for creating
plugins.
Ralph
On Jun 15, 2014, at 2:49 PM, Remko Popma remko.po...@gmail.com wrote:
I see. I agree that the original format is much nicer.
I'd suggest trying the latest developer snapshot of Chainsaw, available at
http://people.apache.org/~sdeboy
Scott
On Jun 11, 2014 8:56 AM, Arthur Hsieh (JIRA) j...@apache.org wrote:
[
[
https://issues.apache.org/jira/browse/LOG4J2-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028637#comment-14028637
]
Scott Deboy commented on LOG4J2-665:
I'd suggest trying the latest developer snapshot
We shouldn't close feature requests as won't fix. Someone may come along
later and decide to implement it.
It's ok to say no one is planning on working on the feature, and remind the
submitter that patches are welcome.
Scott
Scott
On Jun 9, 2014 6:46 AM, Paul Benedict pbened...@apache.org
+1
On Jun 6, 2014 10:07 PM, Matt Sicker boa...@gmail.com wrote:
I like both logos, so I'm good with however you guys would like to go.
Vote or not.
On 6 June 2014 20:57, Remko Popma remko.po...@gmail.com wrote:
Scott, Matt, what do you think?
On Sat, Jun 7, 2014 at 10:48 AM, Ralph Goers
And mine:
DBAHCIEFG
On 6/3/14, Ralph Goers ralph.go...@dslextreme.com wrote:
In case it is not clear, the names (Aragorn, etc) below are for some other
fictional vote to illustrate how to vote
Here is my vote:
DABIEFHGC
Ralph
On Jun 3, 2014, at 1:08 PM, Ralph Goers
Nope, it just shows my personal repositories, even though I am part of
the 'Apache' organization in GitHub.
On 4/14/14, Matt Sicker boa...@gmail.com wrote:
https://travis-ci.org/apache/logging-log4j2
If you log in with your GitHub account, does it give you any administrative
options?
We need to add receivers to log4j2 :)
Dcott
On Mar 25, 2014 5:19 AM, Gary Gregory garydgreg...@gmail.com wrote:
Hi All:
Our server uses v1's org.apache.log4j.net.XMLSocketReceiver.
I do not see a v2 equivalent.
Thoughts?
Gary
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Many of those already exist outside of Apache.
Scott
On Mar 14, 2014 2:29 PM, Matt Sicker boa...@gmail.com wrote:
I see we have log4j, log4net, log4php, and log4cxx. How about Python,
Ruby, Perl, etc.? Anything incubating? Anyone interested in working on one?
--
Matt Sicker boa...@gmail.com
Hi Ralph,
Glad to hear you're getting better!
Scott
On 2/21/14, Gary Gregory garydgreg...@gmail.com wrote:
Ralph,
It is great to hear that you are out of the hospital! Please do take care
of yourself and don't overdo it ;) Log4J can wait... :)
Gary
On Fri, Feb 21, 2014 at 12:19 AM,
: TimeBasedTriggeringPolicy should use event time millis.
Thanks to Robin Zhang Tao.
o LOG4J2-472: BaseConfiguration class does not properly implement
Configuration interface. Thanks to Tal Liron.
o LOG4J2-447: XMLLayout does not include marker name. Thanks to Jeff
Hudren, Mark Paluch, Scott Deboy
I'll check it out..apologies!
On 2/11/14, Remko Popma remko.po...@gmail.com wrote:
Gentle reminder: we need one more PMC vote to be able to release.
On Tuesday, February 11, 2014, Christian Grobmeier grobme...@gmail.com
wrote:
I think Rat is wrong on the jquery license.
They have included
+1
(site looks good, tag built fine with mvn install, artifacts look good)
Scott
On 2/11/14, Scott Deboy scott.de...@gmail.com wrote:
I'll check it out..apologies!
On 2/11/14, Remko Popma remko.po...@gmail.com wrote:
Gentle reminder: we need one more PMC vote to be able to release
couchbase it I won't veto it. Be sure to
change the test package name, too.
Nick
On Feb 7, 2014, at 10:03 AM, Scott Deboy wrote:
+1 to couchbase
On Feb 7, 2014 7:54 AM, Christian Grobmeier grobme...@gmail.com wrote:
On 7 Feb 2014, at 16:19, Nick Williams wrote:
It doesn't so much matter
veto with technical justification. Since I
can't come up with a technical justification for renaming it to couchbase,
I won't veto it. :-)
N
On Feb 7, 2014, at 10:09 AM, Scott Deboy wrote:
I do want to remind everyone that vetoes are only valid if they are backed
by a technical justification
+1 to couchbase
On Feb 7, 2014 7:54 AM, Christian Grobmeier grobme...@gmail.com wrote:
On 7 Feb 2014, at 16:19, Nick Williams wrote:
It doesn't so much matter because the XML element names are case
insensitive, but if we change the plugin name for CouchDB we should
probably also change it
Add setlevel. I also think appender belongs in Api. Yes?
On Jan 31, 2014 10:01 AM, Gary Gregory garydgreg...@gmail.com wrote:
Porting from v1...
We do not have Logger setLevel(Level) because it is not in the LCD API
(Slf4j no, Logback yes, JUL yes).
This sure makes it a pain to port from
Re: appenders, I was thinking about Remko's response here:
http://stackoverflow.com/questions/21303746/migrating-from-log4j-1-2-to-log4j-2-how-to-get-list-of-all-appenders-and-rolli
On 1/31/14, Gary Gregory garydgreg...@gmail.com wrote:
On Fri, Jan 31, 2014 at 1:05 PM, Scott Deboy scott.de
So I assume we could build on this by adding the ability to generate these
custom levels from the config, with no user provided class required?
On Jan 26, 2014 12:58 AM, Ralph Goers ralph.go...@dslextreme.com wrote:
I have completed the work on custom levels. It uses a variation of
Nick’s
, 2014 7:28 AM, Scott Deboy scott.de...@gmail.com wrote:
So I assume we could build on this by adding the ability to generate these
custom levels from the config, with no user provided class required?
On Jan 26, 2014 12:58 AM, Ralph Goers ralph.go...@dslextreme.com
wrote:
I have completed
to directly do that. However, custom levels need to
be mapped to the standard levels in several places. It would be simple to
add support for that wherever you want it. Level.StdLevel.getStdLevel() is
the method used to do that.
Ralph
On Jan 26, 2014, at 7:45 AM, Scott Deboy scott.de...@gmail.com
entail adding a new Levels
element, with sub-elements like Level name=DETAIL intLevel=450 /...
Is that what you are thinking of?
I would be fine with that too, but would like to first focus on generating
the extended Logger interface.
On Mon, Jan 27, 2014 at 5:29 AM, Scott Deboy scott.de
that implementation so that it doesn't have to be
implemented again, and then instantiate/cache the logger instance like
normal.
Make sense?
N
On Jan 26, 2014, at 5:32 PM, Scott Deboy wrote:
Yes that's what I was thinking.
Scott
On Jan 26, 2014 3:18 PM, Remko Popma remko.po...@gmail.com wrote
and it can only be instantiated a single time, so creating
it from the configuration will prevent that.
Ralph
On Jan 26, 2014, at 4:03 PM, Scott Deboy scott.de...@gmail.com wrote:
I have one goal: to remove my request for new built in levels by allowing
the levels to be defined strictly via
If there is a way to support this strictly through configuration that would
be ideal.
I'm trying to find a way to remove my request for additional built in
levels but through configuration instead of adding them ourselves.
Scott
Scott
On Jan 26, 2014 7:38 PM, Nick Williams
to code against. Where is
that compiled interface to come from?
Nick
On Jan 26, 2014, at 9:40 PM, Scott Deboy wrote:
If there is a way to support this strictly through configuration that
would be ideal.
I'm trying to find a way to remove my request for additional built in
levels but through
have something like that it is much easier to argue pro/contra
the new log levels.
On 24 Jan 2014, at 18:36, Scott Deboy wrote:
To be fair, I think we represent a reasonable fraction of the
users..some won't touch new predefined levels, some will use it -
that's the reason for adding
please forgive brief replies and frequent typos
On Jan 26, 2014, at 22:37, Scott Deboy scott.de...@gmail.com wrote:
Yes, I would like to declare in the config:
Level: NOTICE, value: 232
And in Java code be able to use logger.notice(some message).
But I think that'd require invokedynamic
Of course, they'd have to use rhino, or something else...which doesn't
help. Where's duck typing when you need it :)
On 1/26/14, Scott Deboy scott.de...@gmail.com wrote:
Could we leverage Rhino? :)
Scott
On 1/26/14, Nicholas Williams nicho...@nicholaswilliams.net wrote:
Scott
If levels are just a name and a value why require a class at all? What
about just having it defined in the configuration.
On Jan 25, 2014 4:37 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
Because we don't know the class name that the Level belongs to. It is
referenced in the configuration
wrote:
The class is needed because it is a name and a value (two items) that has
to be represented as a single parameter to Logger methods. Using raw int
or String is not a good alternative.
Ralph
On Jan 25, 2014, at 4:54 PM, Scott Deboy scott.de...@gmail.com wrote:
If levels are just a name
names to the configuration and making them be valid. I am
just trying to clean it up a bit based on what Nick is suggesting.
Ralph
On Jan 25, 2014, at 6:30 PM, Scott Deboy scott.de...@gmail.com wrote:
There's no way to add support for users to define level entries (name
and value pairs
They can already do the same thing with loggers right?
Scott
On Jan 25, 2014 10:19 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
A malicious app could do
for (int i=0; i 10; ++i) {
new Level(“Level” + i, 1000 + i){};
}
Sure idiots can do lots of bad things but I don’t think
wrote:
On Thu, Jan 23, 2014 at 11:54 AM, Scott Deboy
scott.de...@gmail.comwrote:
We don't need to scuttle the new levels to support extensible levels.
Of course. The two things are not technically related. That's not what
this is about, though. Since there are camps for and against the new
lets the average Java
programmer fully
understand when he uses what, and maybe even why.
If we have something like that it is much easier to argue pro/contra
the new log levels.
On 24 Jan 2014, at 18:36, Scott Deboy wrote:
To be fair, I think we represent a reasonable fraction
I don't think the two have to be mutually exclusive - we can enhance
'custom level' support via a new mechanism and add built-in support
for the new levels as well.
I personally don't think they're confusing, as folks have mentioned,
httpd uses them.
I used to think of levels as 'severities',
From: Scott Deboy
Date:01/23/2014 11:49 (GMT-05:00)
To: Log4J Developers List
Subject: Re: Levels added in revision 1560602
I don't think the two have to be mutually exclusive - we can enhance
'custom level' support via a new mechanism and add built-in support
for the new levels as well.
I
I don't think we need a vote on the new level code..there's no good
technical reason to ask it to be removed, and it is likely to be
useful to some group of folks.
I think we're doing a good job on the other thread bouncing ideas of
how to handle extensible levels, and that conversation should
me if I'm wrong) anyway. That should give everyone enough time to
explain their position on the new levels before we start the second vote.
Who knows, perhaps we're all in agreement by that time...
On Friday, January 24, 2014, Scott Deboy scott.de...@gmail.com wrote:
I don't think we need
See http://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender
On 1/21/14, Saibabu Vallurupalli saibabu.vallurupa...@gmail.com wrote:
First of all Thanks so much for you all for the quickest response for this
posting. I am thinking of writing a wrapper class and update the
This mechanism is also available in log4j 1.2:
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/rewrite/RewriteAppender.html
On 1/21/14, Scott Deboy scott.de...@gmail.com wrote:
See
http://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender
On 1/21/14, Saibabu
Right, that's what I meant. One trace level.
On Jan 20, 2014 8:15 PM, Gary Gregory garydgreg...@gmail.com wrote:
On Mon, Jan 20, 2014 at 11:08 PM, Scott Deboy scott.de...@gmail.comwrote:
That looks good. Without all the trace levels IMO.
Well, we'd want to keep the ONE TRACE level IMO
+1 for a minimal jar with the servlet support.
On Jan 18, 2014 9:36 AM, Ralph Goers ralph.go...@dslextreme.com wrote:
I’ve always had reservations about the servlet 3.0 automatic configuration
because if the log4j jar is present it can’t be disabled or be modified by
the end user. We’ve had
Expression filter from log4j 1 already supports all of this and hasn't had
to change for years. Markers could be supported as a property with almost
zero work.
On Jan 18, 2014 2:52 PM, Gary Gregory garydgreg...@gmail.com wrote:
On Sat, Jan 18, 2014 at 5:26 PM, Ralph Goers
[
https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862435#comment-13862435
]
Scott Deboy commented on LOG4J2-467:
Here are my results from my Mac - two cached/two
[
https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862435#comment-13862435
]
Scott Deboy edited comment on LOG4J2-467 at 1/4/14 10:55 PM
[
https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862187#comment-13862187
]
Scott Deboy commented on LOG4J2-467:
What should be the bottleneck in this test? I
[
https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862199#comment-13862199
]
Scott Deboy commented on LOG4J2-467:
The test fails part way through for me since
[
https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862217#comment-13862217
]
Scott Deboy commented on LOG4J2-467:
I'm not sure why, but I do get an slf4j error
I think it makes sense to go through the existing bugs and find ones we
feel are critical and squash them before a final 2.0.
Gary's right in the sense that adoption as a non beta means we will feel
resistance to significant changes.
Maybe we should make it clear that Api changes may appear in
I'm on Mac Mavericks, using:
java -version
java version 1.7.0_45
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
admin@spiff:~$
On 11/23/13, Gary Gregory garydgreg...@gmail.com wrote:
On Sat, Nov 23, 2013 at 9:45 AM, Gary
[
https://issues.apache.org/jira/browse/LOG4J2-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13830265#comment-13830265
]
Scott Deboy commented on LOG4J2-447:
I don't think we already have a hamcrest
+1 Everything looks good to me.
On 10/26/13, Jess Holle je...@ptc.com wrote:
Is anyone going to vote on 1.2.17.1?
I'll use this release in any case, but it would be nice if this was the
latest public release in general.
On 10/21/2013 9:26 AM, Christian Grobmeier wrote:
On 21 Oct 2013, at
It's here:
https://logging.apache.org/log4j/extras/download.html
FYI, the main page links 'extras' to the above.
Looks like we need to nuke the other site..
On 10/20/13, Gary Gregory garydgreg...@gmail.com wrote:
Hi All:
I see the 1.1 site here:
Yes, it looks like something went a bit sideways with the -bin jar.
The source jar is correct (no Appender class), but the -bin jar does
have the additional classes in it.
Scott
On 10/20/13, Jess Holle je...@ptc.com wrote:
So I just downloaded apache-log4j-extras-1.2.17-bin.zip, pulled out
, this is weird. So far I have no idea how the Appender.class made it
its way into the -bin artifact.
I will investigate this… any ideas on the error are welcome.
On 20 Oct 2013, at 21:31, Scott Deboy wrote:
Yes, it looks like something went a bit sideways with the -bin jar.
The source jar is correct
wrote:
Do note that the Maven build includes all the duplicates -- I just
checked.
Thus the issue is with the build configuration.
On 10/20/2013 2:33 PM, Gary Gregory wrote:
On Sun, Oct 20, 2013 at 3:31 PM, Scott Deboy scott.de...@gmail.com
mailto:scott.de...@gmail.com wrote:
Yes
I think I fixed it in commit 1534007.
Extras is no longer a 'bundle'.
Scott
On 10/20/13, Christian Grobmeier grobme...@gmail.com wrote:
On 20 Oct 2013, at 21:29, Gary Gregory wrote:
On Sun, Oct 20, 2013 at 3:26 PM, Scott Deboy scott.de...@gmail.com
wrote:
It's here:
https
Gah I committed that on the tag..
sigh..
Sorry
On 10/20/13, Scott Deboy scott.de...@gmail.com wrote:
I think I fixed it in commit 1534007.
Extras is no longer a 'bundle'.
Scott
On 10/20/13, Christian Grobmeier grobme...@gmail.com wrote:
On 20 Oct 2013, at 21:29, Gary Gregory wrote
Reverted...but I see we have -18-snapshot in the pom now..I'll just
remove the bundle packaging entry on trunk..Christian, would you mind
rolling a 1.2.17.1 RC?
Scott
On 10/20/13, Scott Deboy scott.de...@gmail.com wrote:
Gah I committed that on the tag..
sigh..
Sorry
On 10/20/13, Scott
+1
Checked the website, JavaDoc, LICENSE and NOTICE, hashes, built it
with mvn package and tested the dist artifact with Chainsaw, all look
good.
Thanks for your help Christian!
Scott
On 10/14/13, Christian Grobmeier grobme...@gmail.com wrote:
Dear all,
this is a vote for a new Apache
If your examples included loggers I think it would show these added verbose
entries would be another logger at INFO but not a separate severity.
I think of levels in terms of relative numeric severity. DEBUG INFO WARN
ERROR etc. Chainsaw supports this kind of logic in filtering colorizing
and
[
https://issues.apache.org/jira/browse/LOG4J2-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13763772#comment-13763772
]
Scott Deboy commented on LOG4J2-393:
Sounds good - I recall we had a conversation
[
https://issues.apache.org/jira/browse/LOG4J2-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759260#comment-13759260
]
Scott Deboy commented on LOG4J2-393:
I believe this behavior changed when I needed
[
https://issues.apache.org/jira/browse/LOG4J2-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759281#comment-13759281
]
Scott Deboy commented on LOG4J2-393:
This isn't advertiser-specific. I don't believe
[
https://issues.apache.org/jira/browse/LOG4J2-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759278#comment-13759278
]
Scott Deboy commented on LOG4J2-393:
Test:
https://svn.apache.org/repos/asf/logging
Can you include that reply here? Too many mails flying by.
Scott
On Aug 22, 2013 9:16 AM, Gary Gregory garydgreg...@gmail.com wrote:
On Thu, Aug 22, 2013 at 12:09 PM, Ralph Goers
ralph.go...@dslextreme.comwrote:
Why?
See my previous reply.
Gary
On Aug 22, 2013, at 6:25 AM,
See the Column casting in JDBCAppender Column casting in JDBCAppender
thread on the user list for context.
I think it's time to discuss this issue on the dev list. There's no
need for us to say 'no' 20 different ways on the user list when the
reality is that the PGSQL enum issue can be easily
I'm not sure if this ship has fully sailed, but I'd prefer to see us
stick with he dash format due to folks being familiar with it from
log4j 1.
Scott
On 8/16/13, Gary Gregory garydgreg...@gmail.com wrote:
On Fri, Aug 16, 2013 at 1:13 PM, Ralph Goers
ralph.go...@dslextreme.comwrote:
I'm
Is there any way it could be getting loaded in another class loader?
Verbose classes flag help to determine that?
On Aug 16, 2013 10:37 PM, Nick Williams nicho...@nicholaswilliams.net
wrote:
The problem is we don't know what's missing and we can't tell what's
missing. I'm not even convinced
Hey folks,
Now that we have a few guys who are spending a lot of time working to
keep things 'consistent', a friendly reminder to please separate
formatting and 'consistency-related' changes in a separate commit from
bug fixes.
Thanks much,
Scott
I appreciate the commitment to consistently but agree where it isn't
needed, it's reasonable for us as a group to decline to use final where not
strictly required.
On Jul 9, 2013 5:53 PM, Ralph Goers ralph.go...@dslextreme.com wrote:
This topic was covered in an email thread that started with
+1 seems reasonable to me...
On 6/7/13, Nick Williams nicho...@nicholaswilliams.net wrote:
The JBoss Logging devs have accepted my pull request to fix JBLOGGING-94
[1], so JBoss Logging works with Log4j 2 now as of JBoss Logging 3.1.4 and
3.2.0.
However, JBoss Logging still only works with
[
https://issues.apache.org/jira/browse/LOG4J2-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667035#comment-13667035
]
Scott Deboy commented on LOG4J2-238:
Would you mind removing the commented out code
[
https://issues.apache.org/jira/browse/LOG4J2-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663082#comment-13663082
]
Scott Deboy commented on LOG4J2-252:
One implementation idea: Add a Timer
[
https://issues.apache.org/jira/browse/LOG4J2-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661381#comment-13661381
]
Scott Deboy commented on LOG4J2-241:
This already exists in log4j extras. we should
http://www.jetbrains.com/idea/buy/buy.jsp#openSource
On 5/16/13, Gary Gregory garydgreg...@gmail.com wrote:
On Thu, May 16, 2013 at 6:04 PM, Nick Williams
nicho...@nicholaswilliams.net wrote:
I don't use Eclipse (can't stand the thing), so I hesitate to hazard a
guess. My gut feeling is it
Extras sounds ok.
Scott
On May 15, 2013 4:01 AM, Christian Grobmeier grobme...@gmail.com wrote:
Hi,
we have had Apache Companions Extras. Now we don't have subcomponents.
What is the new name now? Is it log4j extras or is it log4j
companions?
I am asking because we need a location for the
I'd prefer if we leave the extra parens. IMO clarity trumps teachable
moments. Just disable the warning?
On May 13, 2013 8:26 AM, Nick Williams nicho...@nicholaswilliams.net
wrote:
It's not 100% harmless, but it is harmless as far as operation of the code.
To understand how it could cause
seem to happen on Friday night when you really
want to go home but it. just. doesn't. work...
Not a fan. :-)
From: Scott Deboy scott.de...@gmail.com
To: Log4J Developers List log4j-dev@logging.apache.org
Sent: Tuesday, May 14, 2013 1:27 AM
Subject: Re: Useless parentheses?
I'd prefer if we
Thanks for posting to the dev list!
I've commented on your stackoverflow post. There were a few issues.
- Stale docs (sorry)
- No support in Chainsaw V2 for Log4j2 socketappenders yet
- Chainsaw wasn't setting up a 'tailing' log file receiver
configuration for the advertised fileappender
Please note, the latest 'release' of Chainsaw doesn't support Log4j2,
only the developer snapshot available here:
http://people.apache.org/~sdeboy
On 5/10/13, Scott Deboy scott.de...@gmail.com wrote:
Thanks for posting to the dev list!
I've commented on your stackoverflow post. There were
to be broken, it's not
really a problem, just a heads up.
--M@
On Fri, May 10, 2013 at 11:48 AM, Scott Deboy scott.de...@gmail.com
wrote:
Thanks for posting to the dev list!
I've commented on your stackoverflow post. There were a few issues.
- Stale docs (sorry)
- No support in Chainsaw V2
of the messages
that should be streaming in. Giving the receiver a level doesn't seem to
fix it either. Any idea what the problem is?
Also it seems that one of the restarts has fixed the horizontal resizing
issue I'd been seeing.
--M@
On Fri, May 10, 2013 at 1:13 PM, Scott Deboy scott.de
, but that's all I can get it to do. Restarting the receiver
doesn't seem to do anything. Double clicking does nothing.
--M@
On Fri, May 10, 2013 at 2:07 PM, Scott Deboy
scott.de...@gmail.comwrote:
When Chainsaw starts you don't need to give it a config, as the config
will be generated once
at 2:18 PM, Scott Deboy scott.de...@gmail.com wrote:
Look in the chainsaw-log tab - there should be messages explaining why
it isn't working.
On 5/10/13, M@ matthew.dun...@gmail.com wrote:
Err, sorry, I meant the URI opens perfectly.
--M@
On Fri, May 10, 2013 at 2:14 PM, M
:
Brilliant! That got it. Thank you so much!
For my next trick I'll play with the format string to get the Logger
column to populate correctly, but that's minor and probably not hard.
--M@
On Fri, May 10, 2013 at 2:24 PM, Scott Deboy scott.de...@gmail.com wrote:
Try this form of URI (note
, M@ matthew.dun...@gmail.com wrote:
Brilliant! That got it. Thank you so much!
For my next trick I'll play with the format string to get the Logger
column to populate correctly, but that's minor and probably not hard.
--M@
On Fri, May 10, 2013 at 2:24 PM, Scott Deboy scott.de
Thanks, taken care of.
On 5/10/13, M@ matthew.dun...@gmail.com wrote:
I edited your SO answer to not contain that mistake, it's awaiting peer
review, do you have the ability to approve it?
--M@
On Fri, May 10, 2013 at 3:40 PM, Scott Deboy scott.de...@gmail.com wrote:
Great!
I need
Scott Deboy created LOG4J2-251:
--
Summary: Support advertisement of configuration text
Key: LOG4J2-251
URL: https://issues.apache.org/jira/browse/LOG4J2-251
Project: Log4j 2
Issue Type
[
https://issues.apache.org/jira/browse/LOG4J2-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13653540#comment-13653540
]
Scott Deboy commented on LOG4J2-251:
Advertising the configuration at the end
[
https://issues.apache.org/jira/browse/LOG4J2-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13653574#comment-13653574
]
Scott Deboy commented on LOG4J2-251:
Expose the XML or JSON configuration text via
[
https://issues.apache.org/jira/browse/LOG4J2-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13648203#comment-13648203
]
Scott Deboy commented on LOG4J2-235:
Is it fair to say 'gui related things
1 - 100 of 465 matches
Mail list logo
