Re: Logo contest?

+ 1 Andreas On 08.05.2013 23:02, Christian Grobmeier wrote: I am sorry to say that I never liked the log4j logo. I always found it 100% ugly. Recently somebody else said, he doesn't know what a green cup has to do with logging. I agree with him. Now the log4j 1.x logo is a green cup. No doubt

Socket Appender error

Hi All, I'm using log4j2 since beta4, now beta5. In general it's a cute library, but there's some bug that I've found out recently : When a client code genreates a huge message ( 64k ), the underlying DatagramOutputStream fails ( UDP socket throws exception). After that all following f

[jira] [Created] (LOG4J2-246) Socket Appender error

Remko Popma created LOG4J2-246: -- Summary: Socket Appender error Key: LOG4J2-246 URL: https://issues.apache.org/jira/browse/LOG4J2-246 Project: Log4j 2 Issue Type: Bug Components: Appen

Re: Socket Appender error

Hi Tomek, Thank you for your bug report! We will take a look. I've created this Jira ticket to track the issue: https://issues.apache.org/jira/browse/LOG4J2-246 Best regards, Remko Sent from my iPhone On 2013/05/09, at 18:34, Tomek Kaczynski wrote: > Hi All, > > >I'm using log4j2 sinc

Re: [VOTE] Log4j 2.0-beta6 rc2

:-/ fair enough. But I would definitely like to put the rush on beta7, like you said. Can someone figure out this bug and go ahead and commit the change so that if the release is canceled for one reason or another the bug will already be fixed? Nick Sent from my iPhone, so please forgive brief re

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652881#comment-13652881 ] Remko Popma commented on LOG4J2-245: Nick, if you need something fast, I cannot commit

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652884#comment-13652884 ] Nick Williams commented on LOG4J2-245: -- Shouldn't if (!stack.isEmpty() && className.

[jira] [Reopened] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reopened LOG4J2-223: -- Assignee: Remko Popma (was: Ralph Goers) Reopening since this is not fixed in beta6 and a te

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652889#comment-13652889 ] Remko Popma commented on LOG4J2-245: Nick, I could be paranoid but the check against a

[jira] [Updated] (LOG4J2-223) IlliegalStateException thrown during Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams updated LOG4J2-223: - Attachment: logging-integration-1.0.0.SNAPSHOT.war Logging-Integration.zip Attach

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652895#comment-13652895 ] Remko Popma commented on LOG4J2-245: About performance though, I wanted to do some pro

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652899#comment-13652899 ] Nick Williams commented on LOG4J2-245: -- You are paranoid :-) ... and slightly incorre

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652903#comment-13652903 ] Remko Popma commented on LOG4J2-245: First, did the modification fix the issue? Secon

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652908#comment-13652908 ] Nick Williams commented on LOG4J2-245: -- Unfortunately, I cannot easily test the modif

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652913#comment-13652913 ] Nick Williams commented on LOG4J2-245: -- Okay, I think I've narrowed it down. Two week

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652915#comment-13652915 ] Nick Williams commented on LOG4J2-245: -- By the way, my JVM /does/ have a class sun.re

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652927#comment-13652927 ] Remko Popma commented on LOG4J2-245: Interesting. I originally thought that the Stack

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652933#comment-13652933 ] Nick Williams commented on LOG4J2-245: -- GOT IT! In Java <= 7, the signature of this

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652943#comment-13652943 ] Nick Williams commented on LOG4J2-245: -- Really, that whole looping-through-methods th

Re: [VOTE] Log4j 2.0-beta6 rc2

I say: let's release beta6 as is now. We have other pending changes for beta7. Gary On Thu, May 9, 2013 at 1:47 AM, Ralph Goers wrote: > How it works is that > a) a release cannot be vetoed. > b) a release must have 3 binding +1 votes (which this does already unless > Ivan or Gary were to chang

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652979#comment-13652979 ] Gary Gregory commented on LOG4J2-245: - Why are we using reflection in the first place?

Re: Logo contest?

Here is one way to do it: https://ianskerrett.wordpress.com/2010/02/24/call-for-community-feedback-on-an-updated-eclipse-logo/ Gary On Thu, May 9, 2013 at 3:15 AM, manyofh wrote: > + 1 > > Andreas > > > On 08.05.2013 23:02, Christian Grobmeier wrote: > >> I am sorry to say that I never liked t

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652990#comment-13652990 ] Nick Williams commented on LOG4J2-245: -- I think the more pertinent question is, why a

[jira] [Comment Edited] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652990#comment-13652990 ] Nick Williams edited comment on LOG4J2-245 at 5/9/13 2:38 PM: --

Re: [VOTE] Log4j 2.0-beta6 rc2

The VOTE rules should be explained on https://commons.apache.org/releases/prepare.html I would rephrase (IIRC, now I cannot find where this is written up): b) a release must have 3 more binding +1 votes than binding -1 votes (which this does already unless Ivan or Gary were to change their vote).

Re: [VOTE] Log4j 2.0-beta6 rc2

Commons? The ASF requirements are at http://www.apache.org/dev/release.html. Ralph On May 9, 2013, at 7:41 AM, Gary Gregory wrote: > The VOTE rules should be explained on > https://commons.apache.org/releases/prepare.html > > I would rephrase (IIRC, now I cannot find where this is written up)

Re: [VOTE] Log4j 2.0-beta6 rc2

On Thu, May 9, 2013 at 11:05 AM, Ralph Goers wrote: > Commons? > Oops, sorry about that! I'm getting my lists mixed up! Gary > > The ASF requirements are at http://www.apache.org/dev/release.html. > > Ralph > > On May 9, 2013, at 7:41 AM, Gary Gregory wrote: > > The VOTE rules should be explai

Re: [VOTE] Log4j 2.0-beta6 rc2

There it is https://www.apache.org/foundation/glossary.html#MajorityApproval Gary On Thu, May 9, 2013 at 11:08 AM, Gary Gregory wrote: > On Thu, May 9, 2013 at 11:05 AM, Ralph Goers > wrote: > >> Commons? >> > > Oops, sorry about that! I'm getting my lists mixed up! > > Gary > > >> >> The ASF

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653006#comment-13653006 ] Ralph Goers commented on LOG4J2-245: The performance benefit of using this class is at

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653017#comment-13653017 ] Remko Popma commented on LOG4J2-245: I was going to commit a change (like the patch ab

[jira] [Comment Edited] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653017#comment-13653017 ] Remko Popma edited comment on LOG4J2-245 at 5/9/13 3:44 PM: I

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653018#comment-13653018 ] Nick Williams commented on LOG4J2-245: -- You can view the change made to the getCaller

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653022#comment-13653022 ] Gary Gregory commented on LOG4J2-245: - FWIW: sun.* classes will not work on IBM JVMs t

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653025#comment-13653025 ] Nick Williams commented on LOG4J2-245: -- Just so I understand (which will help me file

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653031#comment-13653031 ] Remko Popma commented on LOG4J2-245: Same question as Nick... Will the #resolvePackage

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653037#comment-13653037 ] Nick Williams commented on LOG4J2-245: -- Yea, I don't understand what extra informatio

[jira] [Commented] (LOG4J2-229) New JDBC, JPA, and NoSQL Database Appenders for Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653044#comment-13653044 ] Gary Gregory commented on LOG4J2-229: - FYI: As soon as the beta6 VOTE RESULT is announ

[jira] [Updated] (LOG4J2-246) UDP socket Appender error

[ https://issues.apache.org/jira/browse/LOG4J2-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-246: Summary: UDP socket Appender error (was: Socket Appender error) > UDP socket Appender error >

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653088#comment-13653088 ] Nick Williams commented on LOG4J2-245: -- Okay, I've done a little analysis. First, it

[jira] [Comment Edited] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653088#comment-13653088 ] Nick Williams edited comment on LOG4J2-245 at 5/9/13 7:43 PM: --

[jira] [Comment Edited] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653088#comment-13653088 ] Nick Williams edited comment on LOG4J2-245 at 5/9/13 7:44 PM: --

Re: [jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

On Thu, May 9, 2013 at 3:39 PM, Nick Williams (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653088#comment-13653088] > > Nick Williams commented on LOG4J2-245: > --

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653100#comment-13653100 ] Ralph Goers commented on LOG4J2-245: "whoever wrote it" is me. Yes, your understandin

Re: [jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

Oops, I meant to comment in the JIra... sorry. Gary On Thu, May 9, 2013 at 3:48 PM, Gary Gregory wrote: > On Thu, May 9, 2013 at 3:39 PM, Nick Williams (JIRA) wrote: > >> >> [ >> https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-t

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653103#comment-13653103 ] Gary Gregory commented on LOG4J2-245: - Tangent: What about making those "last two bits

[jira] [Created] (LOG4J2-247) SocketServer.isActive should be volatile because it is accessed from different threads

Gary Gregory created LOG4J2-247: --- Summary: SocketServer.isActive should be volatile because it is accessed from different threads Key: LOG4J2-247 URL: https://issues.apache.org/jira/browse/LOG4J2-247 Pr

[jira] [Resolved] (LOG4J2-247) SocketServer.isActive should be volatile because it is accessed from different threads

[ https://issues.apache.org/jira/browse/LOG4J2-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-247. - Resolution: Fixed commit -m "[LOG4J2-247] SocketServer.isActive should be volatile because it is

[jira] [Commented] (LOG4J2-246) UDP socket Appender error

[ https://issues.apache.org/jira/browse/LOG4J2-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653117#comment-13653117 ] Gary Gregory commented on LOG4J2-246: - I have refactored some TCP socket tests in orde

Enable formatting in JIRA

For most of the JIRA project I work on, I am able to use {code:java} and the like to markup comments. Can someone enable this for our project? I've not found a way to do this or I do not have the karma. Thank you, Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence wit

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653129#comment-13653129 ] Nick Williams commented on LOG4J2-245: -- Re Gary's suggestion: I tend to agree with th

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653137#comment-13653137 ] Ralph Goers commented on LOG4J2-245: I'll see if I can look into this in the next few

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653162#comment-13653162 ] Nick Williams commented on LOG4J2-245: -- Ralph, I need to correct something you said.

Re: Enable formatting in JIRA

Yes, PLEASE! +Long.MAX_VALUE On May 9, 2013, at 3:06 PM, Gary Gregory wrote: > For most of the JIRA project I work on, I am able to use {code:java} and the > like to markup comments. > > Can someone enable this for our project? I've not found a way to do this or I > do not have the karma. >

Re: Enable formatting in JIRA

Gary, I think you have all the same permissions that I do. Whatever it is that needs to be changed I don't think we have permission to do it. Ralph On May 9, 2013, at 1:59 PM, Nick Williams wrote: > Yes, PLEASE! > > +Long.MAX_VALUE > > On May 9, 2013, at 3:06 PM, Gary Gregory wrote: > >> F

[jira] [Created] (LOG4J2-248) Log4jContextListener: Use Thread instead of Class for fallback classloader

Tim Tucker created LOG4J2-248: - Summary: Log4jContextListener: Use Thread instead of Class for fallback classloader Key: LOG4J2-248 URL: https://issues.apache.org/jira/browse/LOG4J2-248 Project: Log4j 2

[jira] [Commented] (LOG4J2-248) Log4jContextListener: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653360#comment-13653360 ] Nick Williams commented on LOG4J2-248: -- I don't think PMD is used to web applications

[jira] [Created] (LOG4J2-249) Log4jContextListener: Support property substitution in context-params

Tim Tucker created LOG4J2-249: - Summary: Log4jContextListener: Support property substitution in context-params Key: LOG4J2-249 URL: https://issues.apache.org/jira/browse/LOG4J2-249 Project: Log4j 2

[jira] [Created] (LOG4J2-250) (TBD) Only create ThrowableProxy if it is used in configuration

Remko Popma created LOG4J2-250: -- Summary: (TBD) Only create ThrowableProxy if it is used in configuration Key: LOG4J2-250 URL: https://issues.apache.org/jira/browse/LOG4J2-250 Project: Log4j 2

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653376#comment-13653376 ] Remko Popma commented on LOG4J2-245: I created LOG4J2-250 to separate the performance

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653378#comment-13653378 ] Remko Popma commented on LOG4J2-245: With regards to what would be the correct defensi

[jira] [Commented] (LOG4J2-245) EmptyStackException when logging error through JCL bridge

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653386#comment-13653386 ] Nick Williams commented on LOG4J2-245: -- No. If the stack is empty, it will get this i

[jira] [Commented] (LOG4J2-248) Log4jContextListener: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653388#comment-13653388 ] Tim Tucker commented on LOG4J2-248: --- The warning is actually one of the few in their J2E

[jira] [Commented] (LOG4J2-248) Log4jContextListener: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653392#comment-13653392 ] Tim Tucker commented on LOG4J2-248: --- It looks like more recent versions of Struts actual

[jira] [Commented] (LOG4J2-248) Log4jContextListener: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653394#comment-13653394 ] Remko Popma commented on LOG4J2-248: Nice detective work, Tim! > Log4

[jira] [Updated] (LOG4J2-245) EmptyStackException when logging exceptions with Log4J2 in Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-245: --- Description: [Note: the description below is the original error report. After analysis it turned out

[jira] [Commented] (LOG4J2-249) Log4jContextListener: Support property substitution in context-params

[ https://issues.apache.org/jira/browse/LOG4J2-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653421#comment-13653421 ] Ralph Goers commented on LOG4J2-249: That is a great idea! Feel free to provide a pat

[jira] [Commented] (LOG4J2-248) Log4jContextListener: Use Thread instead of Class for fallback classloader

[ https://issues.apache.org/jira/browse/LOG4J2-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653423#comment-13653423 ] Ralph Goers commented on LOG4J2-248: Thanks. It might make sense to make the behavior

Re: Enable formatting in JIRA

Does this help? https://confluence.atlassian.com/display/JIRA/Configuring+Renderers Sent from my iPhone On 2013/05/10, at 6:55, Ralph Goers wrote: > Gary, I think you have all the same permissions that I do. Whatever it is > that needs to be changed I don't think we have permission to do it.

Re: Enable formatting in JIRA

Actually we're on version 5.2 so maybe this is better: https://confluence.atlassian.com/display/JIRA052/Configuring+Renderers Sent from my iPhone On 2013/05/10, at 9:48, Remko Popma wrote: > Does this help? > https://confluence.atlassian.com/display/JIRA/Configuring+Renderers > > > Sent from

[jira] [Created] (LOG4J2-251) Support advertisement of configuration text

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: Improveme

Re: Enable formatting in JIRA

Right. But when I look at https://issues.apache.org/jira/plugins/servlet/project-config/LOG4J2/fields I cannot change the renderer. Gary On Thu, May 9, 2013 at 8:52 PM, Remko Popma wrote: > Actually we're on version 5.2 so maybe this is better: > https://confluence.atlassian.com/display/JIRA

[jira] [Commented] (LOG4J2-251) Support advertisement of configuration text

[ https://issues.apache.org/jira/browse/LOG4J2-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653540#comment-13653540 ] Scott Deboy commented on LOG4J2-251: Advertising the configuration at the end of basec

Re: Enable formatting in JIRA

Hmm, this https://confluence.atlassian.com/display/JIRA052/Specifying+Field+Behaviour says "Log in as a user with the *JIRA Administrators* global permission ." Gary On Fri, May 10, 2013 at 12:35 AM, Gary Gregory wro

[jira] [Resolved] (LOG4J2-251) Support advertisement of configuration text

[ https://issues.apache.org/jira/browse/LOG4J2-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Deboy resolved LOG4J2-251. Resolution: Fixed Fix committed in svn trunk revision 1480877 Commit msg: Expose the XML or JSON

Re: Enable formatting in JIRA

Are you in the jira-administrators group? Sent from my iPhone On 2013/05/10, at 13:39, Gary Gregory wrote: > Hmm, this > https://confluence.atlassian.com/display/JIRA052/Specifying+Field+Behaviour > > says "Log in as a user with the JIRA Administrators global permission." > > Gary > > > O

Re: Enable formatting in JIRA

Someone on the PMC is an ASF officer (I don't know who), and my bet is all ASF officers have this global permission. However, as it sounds like this change will affect multiple projects and not just Log4j2, there may be some resistance to making the change. (To which I would reply, "Why? Why on

Re: Enable formatting in JIRA

It is possible to set up project-specific pages do that our changes don't affect others. Sent from my iPhone On 2013/05/10, at 13:50, Nick Williams wrote: > Someone on the PMC is an ASF officer (I don't know who), and my bet is all > ASF officers have this global permission. > > However, as

[jira] [Commented] (LOG4J2-251) Support advertisement of configuration text

[ https://issues.apache.org/jira/browse/LOG4J2-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653574#comment-13653574 ] Scott Deboy commented on LOG4J2-251: Expose the XML or JSON configuration text via the

Re: [VOTE] Log4j 2.0-beta6 rc2

My +1 Ralph On May 6, 2013, at 8:52 PM, Ralph Goers wrote: > This is a vote to release Log4j 2.0-beta6, the eighth release of Log4j 2.0. > This is the second release candidate which fixes issues with a few missing > license headers and some findbugs issues. > > Changes in this version include

[RESULT][VOTE] Log4j 2.0-beta6 rc2

This vote has passed with +1s from Ralph Goers (binding) Gary Gregory (binding) Ivan Habunek (binding) Christian Grobmeier (binding) Oliver Lamy Remko Popma The vote received 1 -1 vote from Nick Williams. I will continue with the release process. Thank you for taking the time to review the relea