[
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964547#comment-13964547
]
Nick Williams commented on LOG4J2-599:
--
I would disagree with the notion that we
[
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964339#comment-13964339
]
Nick Williams edited comment on LOG4J2-599 at 4/9/14 4:2
[
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964339#comment-13964339
]
Nick Williams commented on LOG4J2-599:
--
To be clear, {{toString}} of a {{Supp
[
https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963807#comment-13963807
]
Nick Williams commented on LOG4J2-599:
--
I've been thinking about this
That would work if he was parsing the JSON manually, which is itself an
extremely complex thing to do. It sounds like he's using Jackson—and rightly
so. I'm not entirely sure how to do this with Jackson, but I help out with the
development over there from time to time, and I can ask the mailing
I'm not convinced we need it, but it was put there to make Level as close to a
real enum as possible. Every enum provides that static method (by way of
extending Enum).
N
On Mar 25, 2014, at 7:28 AM, Gary Gregory wrote:
> Why do we have this API in org.apache.logging.log4j.Level:
>
> publ
[
https://issues.apache.org/jira/browse/LOG4J2-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911208#comment-13911208
]
Nick Williams commented on LOG4J2-474:
--
I'll take care of this, Tal. T
[
https://issues.apache.org/jira/browse/LOG4J2-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-474:
Assignee: Nick Williams
> MongoDBProvider won't work with databases that do
I don't think it should even say WHO signed it. It already instructs users to
download the KEYS file and import that file. Isn't that sufficient? As long as
the artifacts are signed by someone in that KEYS file, doesn't that take care
of it? Why does this page need to list someone's name?
Nick
ks again!
>
>
> On 16 Feb 2014, at 21:19, Nick Williams wrote:
>
>> The Apache Log4j 2 team is proud to announce the Log4j 2.0-rc1 release!
>>
>> Apache Log4j is a well known framework for logging application behavior.
>> Log4j 2 is an upgrade to Log4j
nosql.mongo package to
org.apache.logging.log4j.core.appender.db.nosql.mongodb.
o Renamed the org.apache.logging.log4j.core.appender.db.nosql.couch package to
org.apache.logging.log4j.core.appender.db.nosql.couchdb.
o LOG4J2-507: Space Level numbers by 100 instead of 1.
o LOG4J2-41: Add support for custom logging levels. Thanks to Nick
I got through step 12-J in the release guide
(https://wiki.apache.org/logging/Log4j2ReleaseGuide), but I can't perform step
12-K (committing everything to dist). I was told I was "forbidden" from
committing.
Help?
Nick
On Feb 12, 2014, at 9:49 PM, Nick Williams wrote:
> Th
The vote passes with +1s from:
Remko Popma (binding)
Nick Williams
Christian Grobmeier (binding)
Scott Deboy (binding)
Matt Sicker
There were no +0s or -1s.
I will continue with the release process. I still need to publish my keys to
KEYS, so if anyone can tell me how to edit that file, I&#
[
https://issues.apache.org/jira/browse/LOG4J2-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899307#comment-13899307
]
Nick Williams commented on LOG4J2-536:
--
H. This might be a Maven bug.
te:
> RAT complains:
>
> ***
>
> Unapproved licenses:
>
> src/site/resources/js/jquery.js
> src/site/resources/js/jquery.min.js
>
> ***
> I'm not sure what our policy is for this kind of issue.
>
> Gary
>
>
>
> On Mon, Feb 1
On Feb 9, 2014, at 1:56 PM, Nick Williams wrote:
> This is a vote to release Log4j 2.0-rc1, the twelfth release of Log4j 2.0.
>
>
>
> Please test and cast your votes.
> [x] +1, release the artifacts
> [ ] -1, don't release because...
Nick
wrote:
> So does JDK8 add that security restriction to getCallerClass(int) as well?
>
>
> On 9 February 2014 13:57, Nick Williams wrote:
> Yes. The C++ code enforces the restriction. I've edited it, so I know it
> first hand. :-)
>
> Nick
>
> On Feb 9,
Yes. The C++ code enforces the restriction. I've edited it, so I know it first
hand. :-)
Nick
On Feb 9, 2014, at 1:51 PM, Matt Sicker wrote:
> Then I'm guessing abuse of JNI is out of the question, too?
>
>
> On 9 February 2014 13:41, Nick Williams wrote:
>
There have been extensive discussions about getCallerClass(), which you can
find throughout the archives of the developer's list and the JDK core-libs-dev
list. In very abbreviated form, only privileged, JDK code can call
getCallerClass(). They initially removed getCallerClass(int), but we convi
ps://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
>
> looks like i would need to downgrade maven to 3.0.
>
> Weird, i never saw this before
>
> On 9 Feb 2014, at 19:28, Nick Williams wrote:
>
>> I disabled the site plugin on the distribution module and that f
Furthermore, I'm doing this like the Wiki
(https://wiki.apache.org/logging/Log4j2ReleaseGuide) says:
If the release fails after sending the vote email:
...
2. Rename the release tag in subversion to add rcn to the end of the tag.
Nick
On Feb 9, 2014, at 1:22 PM, Nick Williams wrote:
&
That is not how we have done it in the past. We have never done it that way.
When releasing beta8, we originally created the tag log4j-2.0-beta8. When the
vote failed, we renamed that tag to log4j-2.0-beta8-rc1 and re-created the tag
log4j-2.0-beta8. The vote on that tag passed. This is clearly
understand whats your problem too
>
>
> On 9 Feb 2014, at 18:42, Nick Williams wrote:
>
>> I checked out a fresh trunk anyway and built site again. Same error, so it's
>> not something wrong with my local copy. I don't understand...and we can't
>> release
I checked out a fresh trunk anyway and built site again. Same error, so it's
not something wrong with my local copy. I don't understand...and we can't
release until this is fixed. :-(
N
On Feb 9, 2014, at 11:14 AM, Nick Williams wrote:
> No, that's not it. It's lo
runk/src/site/site.vm
>
> Does it exist on your system? If not maybe you should work on on a fresh
> checkout.
>
> On 9 Feb 2014, at 7:56, Nick Williams wrote:
>
>> By the way, this is the error I'm getting when building site now:
>>
>> [ERROR] Failed to e
bution/src/site/site.vm'
does not exist -> [Help 1]
As far as I can tell, nothing has changed with the log4j-distribution project
since it worked this morning. I'm at a loss to explain this sudden failure.
Help?
N
On Feb 9, 2014, at 12:43 AM, Nick Williams wrote:
> I'm
I'm giving up for today. First pass: Resulted in a canceled vote. Second pass:
Sonatype crashed halfway through and stopped accepting uploads to the staging
repository. Third pass: Now `mvn site` fails with strange error about a missing
file that it shouldn't be looking for to begin with. I give
Ahh. The class was originally abstract, hence why the methods were final. I see
now why that's not needed. My bad.
N
On Feb 9, 2014, at 12:34 AM, Gary Gregory wrote:
> On Sun, Feb 9, 2014 at 1:22 AM, Nick Williams
> wrote:
> Gary,
>
> One of your commits tonight change
Gary,
One of your commits tonight changed all of the methods in Level from being
final to being non-final. This is not what we agreed upon. Why did you make
this change? Was this one of the auto-refactor changes? I've noticed a lot of
cleanup tonight that smells like that. :-)
Nick
---
I didn't. I renamed the tag to ...2.0-rc1-rc1. But when I tried to roll 2.0-rc1
RC2, Sonatype crashed halfway through the release and stopped responding.
THAT'S the tag I deleted, as clearly shown by the commit logs.
N
On Feb 9, 2014, at 12:12 AM, Gary Gregory wrote:
>
>
>
>
> Never delete
On Feb 8, 2014, at 11:13 PM, Remko Popma wrote:
>
> On Sun, Feb 9, 2014 at 1:31 PM, Nick Williams
> wrote:
> Well, unfortunately my first release attempt didn't turn out so well. The
> vote for Log4j 2.0-rc1 RC1 has been canceled:
>
> - There are unsupported
Feb 9, 2014 at 1:55 PM, Nick Williams
> wrote:
> In changes.xml, I see some committers put changes at the top of a
> and others put changes at the bottom of a . Which is the best
> practice?
>
> Nick
> -
In changes.xml, I see some committers put changes at the top of a and
others put changes at the bottom of a . Which is the best practice?
Nick
-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional com
Well, unfortunately my first release attempt didn't turn out so well. The vote
for Log4j 2.0-rc1 RC1 has been canceled:
- There are unsupported licenses. I will fix those shortly.
- There might be something pointing to rc2 instead of rc1. I'll look into that.
Gary also pointed out LOG4J2-531, re
>>
>> Ralph, get well soon!
>> -Remko
>>
>>
>> On Sunday, February 9, 2014, Nick Williams
>> wrote:
>> Turns out my email address in Sonatype is not correct (it's just my Apache
>> ID, "nickwilliams," instead of my Apache emai
. I've emailed Infra to get my email address corrected,
since it's read-only in Sonatype.
Nick
On Feb 8, 2014, at 2:52 PM, Christian Grobmeier wrote:
> On 8 Feb 2014, at 21:12, Nick Williams wrote:
>
>> Almost done. In the vote email, I'm supposed to, "Provide a lis
Nick
On Feb 8, 2014, at 1:17 PM, Christian Grobmeier wrote:
> On 8 Feb 2014, at 20:11, Nick Williams wrote:
>> On Feb 8, 2014, at 1:06 PM, Christian Grobmeier wrote:
>>> OK, so just confirming you want me to do:
>>> svn delete
>>> https://svn.apac
On Feb 8, 2014, at 1:06 PM, Christian Grobmeier wrote:
> Nick,
>
> i totally feel your pain. Releasing is always evil, i never experienced it
> otherwise in what ever project.
>
> On 8 Feb 2014, at 19:56, Nick Williams wrote:
>> Well, after wasting a couple hours, it
figuration."
I need someone to:
- Delete the rc1 tag, please.
- Either give me permissions to roll a release, or just do it for me. I've
already run steps 1-5. The release notes have been committed.
Nick
On Feb 8, 2014, at 12:13 PM, Nick Williams wrote:
> Christian was right. The d
bunch of times
> to set they version. I have never gotten messages like below when releasing.
>
> Sent from my iPad
>
> On Feb 8, 2014, at 9:02 AM, Nick Williams
> wrote:
>
>> The wiki does NOT have enough info on this...
>>
>> I got the following
expression ${project.version}
[INFO] Ignoring artifact version update for expression ${project.version}
[INFO] Ignoring artifact version update for expression ${project.version}
[INFO] Ignoring artifact version update for expression ${project.version}
[INFO] Ignoring artifact version update fo
Figured it out! The Wiki doesn't say to change the Log4jReleaseVersion
property. *mental note to fix this*
Nick
On Feb 8, 2014, at 10:36 AM, Nick Williams wrote:
> *sigh* I got stuck on step TWO. TWO!
>
> • Run "mvn -P release-notes generate-resources" to cre
If someone could point out to me how to tell Maven to generate release notes
for rc1, that would be great. Google is useless because it removes the hyphen
from the Maven command, so my only search results are release notes for Maven.
Nick
On Feb 8, 2014, at 10:07 AM, Nick Williams wrote:
>
nd
>> HttpComponenent, it's not exactly something I'd call 'fun'.
>>
>> You might need to be on the PMC, I'm not sure, Ralph?
>>
>> Gary
>>
>>
>>
>> On Fri, Feb 7, 2014 at 11:55 PM, Nick Williams
>> wrote:
>> I hav
cus on OSGi for RC2...
>
> Gary
>
>
> On Fri, Feb 7, 2014 at 10:31 PM, Nick Williams
> wrote:
> Let's roll 2.0-rc1 tonight. We've all basically agreed that there are no
> showstoppers. I've fixed a whole bunch of appender-related bugs, and there's
> no iss
Let's roll 2.0-rc1 tonight. We've all basically agreed that there are no
showstoppers. I've fixed a whole bunch of appender-related bugs, and there's no
issue with the Servlet 3.0 auto-initialization. Can someone kick that off so
that we can have a vote this weekend and get this out there ASAP?
many database vendors these days. What do you think?
>
> Thanks!
>
>
> On 7 Feb 2014, at 17:55, Nick Williams wrote:
>
>> Ohhh okay. I misunderstood. H. Well I suppose in that case we really
>> must rename it, although I'm not super happy about it. But
Yes, I'm confused by this addition to. Why did we do this?
Nick
On Jan 30, 2014, at 12:24 AM, Gary Gregory wrote:
> I'm slightly confused by this addition because it seems redundant with using
> StringFormattedMessage and StringFormattedMessageFactory
>
> Gary
>
> --
> E-Mail: garydgreg...@
[
https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-444.
--
Resolution: Not A Problem
Assignee: Nick Williams
According to the [EclipseLink logging
[
https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-475.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565889. Based it off of Matt&#
[
https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-475:
Assignee: Nick Williams
> MongoDBConnection is broken because it uses addDecodingH
[
https://issues.apache.org/jira/browse/LOG4J2-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-489.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-457.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-442.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-407.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-438.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-457:
Assignee: Nick Williams
> JDBCAppender does not release JDBC connections to the connect
[
https://issues.apache.org/jira/browse/LOG4J2-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-489:
Assignee: Nick Williams
> Should JPADatabaseManager being using so many transacti
[
https://issues.apache.org/jira/browse/LOG4J2-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-442:
Assignee: Nick Williams
> Log4j2 Database insert problem in Websph
[
https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams closed LOG4J2-422.
Closing because not an issue anymore.
> DriverManager for JDBC Appender should have argument
[
https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-422.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
This issue is fixed with r1565838. However
cp?
>
>
> On 5 February 2014 18:07, Remko Popma wrote:
>
>
> On Thursday, February 6, 2014, Nick Williams
> wrote:
>
> On Feb 5, 2014, at 5:52 PM, Remko Popma wrote:
>
>>
>>
>> On Thursday, February 6, 2014, Nick Williams
>> wrote:
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894889#comment-13894889
]
Nick Williams commented on LOG4J2-529:
--
Yes, {{webapp30.war}} won't work
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894853#comment-13894853
]
Nick Williams commented on LOG4J2-529:
--
I just tried a different approach an
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894841#comment-13894841
]
Nick Williams commented on LOG4J2-529:
--
I still can't duplicate this. I d
f veto.
>>
>> I would like to see folks ask questions and talk about concerns, and then
>> only mention a veto when there is no other recourse.
>> On Feb 7, 2014 8:14 AM, "Nick Williams"
>> wrote:
>>
>>> Yep. I would've accompanied any veto
valid if they are backed by
> a technical justification.
>
> Scott
>
> On Feb 7, 2014 8:07 AM, "Nick Williams" wrote:
> I'm not convinced it really makes a difference, but it's better than couchdb,
> so if the majority wants couchbase it I won't vet
2014 7:54 AM, "Christian Grobmeier" 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 for MongoDB. T
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
for MongoDB. There's a reason I did that, I just can't remember what it was...
I don't see any compelling reason to rename the package. The
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894616#comment-13894616
]
Nick Williams commented on LOG4J2-529:
--
Remko, here's your problem:
{code:
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894172#comment-13894172
]
Nick Williams commented on LOG4J2-529:
--
Remko, I can't reproduce it. Works
On Feb 5, 2014, at 5:52 PM, Remko Popma wrote:
>
>
> On Thursday, February 6, 2014, Nick Williams
> wrote:
> Guys,
>
> Currently, the JDBCAppender allows users to specify a mechanism for
> connecting to the database using one of three options:
>
> - DataSour
Guys,
Currently, the JDBCAppender allows users to specify a mechanism for connecting
to the database using one of three options:
- DataSourceConnectionSource: Looks up a JNDI data source
- FactoryMethodConnectionSource: User specifies a class and static method for
retrieving connections
- Drive
Maybe he'll respond again tonight and let us know if he's set on 2.0 or fine
with 2.0.0. :-)
N
On Feb 4, 2014, at 1:42 AM, Gary Gregory wrote:
> I'm happy to let Ralph pick, either way is fine with me.
>
> Gary
>
>
> On Tue, Feb 4, 2014 at 2:27 AM, Ni
.0 in the book. I'm OK with 2.0
> and 2.0.0 even though 2.0.0 feels redundant. Like someone else posted I find
> the .FINAL and -RELEASE and whatnot ludicrous.
>
> Gary
>
>
> On Tue, Feb 4, 2014 at 2:14 AM, Nick Williams
> wrote:
> Well well well. I'm sen
sion number be?
> >>
> >> Also 2.0 or 2.0.0 for me
> >>
> >> On 3 Feb 2014, at 7:41, Ralph Goers wrote:
> >>
> >>> I had thought it would be 2.0.
> >>>
> >>> Sent from my iPad
> >>>
> >>>> On F
On Mon, Feb 3, 2014 at 6:36 PM, Nick Williams
> wrote:
> Wow. This is going to be hard...
>
> I have submitted my nominations. What's the next step? I read the JIRA, but I
> saw nothing talking about this "nomination" stage on the Wiki. IMO, doing the
> *actual*
Wow. This is going to be hard...
I have submitted my nominations. What's the next step? I read the JIRA, but I
saw nothing talking about this "nomination" stage on the Wiki. IMO, doing the
*actual* voting on the mailing list is preferable. Voting on the wiki will be
hard and discourage particip
> Sent from my iPad
>>
>>> On Feb 2, 2014, at 8:59 PM, Nick Williams
>>> wrote:
>>>
>>> I'm finalizing the logging chapter of my book to send to the printers
>>> Wednesday (I'm so glad I got to correct it to say Level was extendabl
My wiki name is NickWilliams.
Nick
On Feb 3, 2014, at 4:10 AM, Christian Grobmeier wrote:
> Hello,
>
> yes, there is a reason! Please give me your wiki name.
>
> You need to be added to the contributors group.
>
> I will add a note to the wiki page as well
>
> Cheers
> Christian
>
> On 3 Fe
I'm finalizing the logging chapter of my book to send to the printers Wednesday
(I'm so glad I got to correct it to say Level was extendable!), and I need to
know what the Maven artifact GA version number will be. I print the new Maven
artifacts used in each chapter on the first page of the chap
Matt and I coordinated off-list today and got our presentation proposals
submitted to ApacheCon. Assuming they're all accepted, Log4j will have four
presentations representing it. Go us!
Nick
On Jan 31, 2014, at 11:25 PM, Nick Williams wrote:
> Matt, sorry for the delay. I've h
that would work. Nashville huh? My co-worker is from there too, neat.
>
> In regard to the async and such, I think that'd be a great idea. One of the
> selling points of log4j over logback is performance, right?
>
> Matt Sicker
>
> On Jan 31, 2014, at 0:52, Nick Williams wr
On Jan 31, 2014, at 3:29 PM, Gary Gregory wrote:
> On Fri, Jan 31, 2014 at 2:00 PM, Nick Williams
> wrote:
> I do not think appenders should be in the API. Appenders are pretty much the
> definition of an implementation detail.
>
> As for setLevel, I absolutely think it
Tsk tsk. Using auto-refactor again without checking the output. :-P
N
On Jan 31, 2014, at 7:40 AM, Gary Gregory (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887754#comment-1388
[
https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888026#comment-13888026
]
Nick Williams commented on LOG4J2-500:
--
It can be both.
If a web application
I do not think appenders should be in the API. Appenders are pretty much the
definition of an implementation detail.
As for setLevel, I absolutely think it's a problem point when migrating from
Log4j 1 to Log4j 2. In my Log4j 1 apps, I offer a simple admin console for
changing the log levels of
On Jan 30, 2014, at 9:25 PM, Matt Sicker wrote:
> On 30 January 2014 18:01, Nick Williams wrote:
> Matt,
>
> Do you want to share a hotel room? I know it would certainly help my finances
> to split one, and depending on whether you get employer support, it should
> prob
er logging APIs not already implemented, creating
> additional components (I.e., appenders, filters, layouts, etc.), and many
> other ideas. Obviously that's too much to cover in one talk, but it's a good
> place to start examining what topics to cover and at what levels of expert
[
https://issues.apache.org/jira/browse/LOG4J2-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886359#comment-13886359
]
Nick Williams commented on LOG4J2-522:
--
-0: Paul has suggested we hold off on &q
[
https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-323.
--
Resolution: Fixed
Fixed with r1562688. Please verify and close.
> ThreadLocal-leak on tom
[
https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reopened LOG4J2-323:
--
Remko,
Nulling out the reference to the {{ThreadLocal}} is not enough (in fact, it's
not
ecting Loggers using
> annotations.
>
>
> On 29 January 2014 07:46, Remko Popma wrote:
>
>
> On Wednesday, January 29, 2014, Nick Williams
> wrote:
>
> On Jan 28, 2014, at 5:43 PM, Remko Popma wrote:
>
>> I would really like everyone's feedback o
[
https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885070#comment-13885070
]
Nick Williams commented on LOG4J2-245:
--
Max, I cannot replicate this in
[
https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885059#comment-13885059
]
Nick Williams commented on LOG4J2-444:
--
Hemri, it occurred to me that you could
[
https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885056#comment-13885056
]
Nick Williams commented on LOG4J2-492:
--
Remko, what's the status on this? I
[
https://issues.apache.org/jira/browse/LOG4J2-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885054#comment-13885054
]
Nick Williams commented on LOG4J2-508:
--
Can we close this as won't fix no
[
https://issues.apache.org/jira/browse/LOG4J2-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885049#comment-13885049
]
Nick Williams commented on LOG4J2-452:
--
Documentation updated with r156
[
https://issues.apache.org/jira/browse/LOG4J2-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885050#comment-13885050
]
Nick Williams commented on LOG4J2-512:
--
Documentation updated with r156
On Jan 28, 2014, at 5:43 PM, Remko Popma wrote:
> I would really like everyone's feedback on this. I have two questions:
>
> 1. Does this fulfill everyone's requirements?
> Another way of asking this is: would you use this in your own projects? (If
> not, why not?)
Personally, no. I don't like
1 - 100 of 642 matches
Mail list logo
