[
https://issues.apache.org/jira/browse/LOG4J2-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Grobmeier updated LOG4J2-316:
---
Description:
h4. Log4J logo contest
THANK YOU FOR PARTICIPATING - we are going to ch
[
https://issues.apache.org/jira/browse/LOG4J2-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1386#comment-1386
]
Christian Grobmeier commented on LOG4J2-316:
THANK YOU FOR PARTICIPATING - we
Hi all,
please show your support for your favorite logo on this wiki page:
http://wiki.apache.org/logging/Log4jLogoNominations
I added a few nominations already, just stick with the format.
Everybody reading this message is invited to nominate their favorite logo.
Cheers,
Christian
---
Remko Popma created LOG4J2-525:
--
Summary: Broken link to RoutingAppender at bottom of
PropertySubstitution section on Config page
Key: LOG4J2-525
URL: https://issues.apache.org/jira/browse/LOG4J2-525
Pro
I do not think we need jiras to track small doc fixes...
Gary
Original message
From: "Remko Popma (JIRA)"
Date:02/02/2014 07:52 (GMT-05:00)
To: log4j-dev@logging.apache.org
Subject: [jira] [Created] (LOG4J2-525) Broken link to RoutingAppender at
bottom of PropertySubstit
Was away from PC. Reminder.
On Sunday, February 2, 2014, Gary Gregory wrote:
> I do not think we need jiras to track small doc fixes...
>
> Gary
>
>
> Original message
> From: "Remko Popma (JIRA)"
> Date:02/02/2014 07:52 (GMT-05:00)
> To:
> log4j-dev@logging.apache.org
> Subje
[
https://issues.apache.org/jira/browse/LOG4J2-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-345:
---
Attachment: 0001-Add-log4j-1.x-OSGi-bundle.patch
Here you go. One patch for adding the 1.x API as ano
[
https://issues.apache.org/jira/browse/LOG4J2-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-525.
--
> Broken link to RoutingAppender at bottom of PropertySubstitution section on
> Config page
>
[
https://issues.apache.org/jira/browse/LOG4J2-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-525.
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed in revision 1563732.
> Broken link to Routin
[
https://issues.apache.org/jira/browse/LOG4J2-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889086#comment-13889086
]
Matt Sicker commented on LOG4J2-400:
I believe there are many, many ways to implement
[
https://issues.apache.org/jira/browse/LOG4J2-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889088#comment-13889088
]
Matt Sicker commented on LOG4J2-373:
Shouldn't you be loading the bundles like so: log
Christian,
Maybe I'm missing something, but I don't see a link to edit this page...
In the Actions bar (left of Info, Attachments, More Actions) I see
"Immutable Page" in gray (not a link)...
Can you check?
Remko
On Sunday, February 2, 2014, Christian Grobmeier
wrote:
> Hi all,
>
> please sho
[
https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-475:
---
Attachment: 0001-Fix-LOG4J2-475.patch
Here's a patch.
> MongoDBConnection is broken because it uses
[
https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889216#comment-13889216
]
Matt Sicker commented on LOG4J2-407:
One possibility would be to use Commons Pool for
Matt Sicker created LOG4J2-526:
--
Summary: Support MongoDB connection URL in configuration
Key: LOG4J2-526
URL: https://issues.apache.org/jira/browse/LOG4J2-526
Project: Log4j 2
Issue Type: Wish
Same, can't edit the page.
On 2 February 2014 19:18, Remko Popma wrote:
> Christian,
>
> Maybe I'm missing something, but I don't see a link to edit this page...
> In the Actions bar (left of Info, Attachments, More Actions) I see
> "Immutable Page" in gray (not a link)...
>
> Can you check?
>
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
I vote for 2.0.0... and my vote is non-binding. :-)
On Sun, Feb 2, 2014 at 10:59 PM, Nick Williams <
nicho...@nicholaswilliams.net> 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 extendable!),
> and I n
I like short names (and to me, 2.0 doesn't conflict with a subsequent
2.0.1),
so either 2.0 or 2.0.0 would be my preference.
(But no strong preference. Other name is fine too.)
Remko
On Monday, February 3, 2014, Paul Benedict wrote:
> I vote for 2.0.0... and my vote is non-binding. :-)
>
>
> O
You have to log in to the wiki
Sent from my iPad
> On Feb 2, 2014, at 8:49 PM, Matt Sicker wrote:
>
> Same, can't edit the page.
>
>
>> On 2 February 2014 19:18, Remko Popma wrote:
>> Christian,
>>
>> Maybe I'm missing something, but I don't see a link to edit this page...
>> In the Actions
I had thought it would be 2.0.
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 extendable!), and
> I need to know what the Maven arti
21 matches
Mail list logo
