[
https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137862#comment-16137862
]
Ralph Goers commented on LOG4J2-1925:
-
The first time I ran the test with my Processo
[
https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137851#comment-16137851
]
Trejkaz commented on LOG4J2-1925:
-
I just retested myself, but I lost my own code which p
Hi All,
Looking for help to fix this or document a workaround:
https://issues.apache.org/jira/browse/LOG4J2-2009
Gary
[
https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137496#comment-16137496
]
ASF subversion and git services commented on LOG4J2-2009:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137494#comment-16137494
]
ASF subversion and git services commented on LOG4J2-2009:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137482#comment-16137482
]
Gary Gregory commented on LOG4J2-2009:
--
I added the unit test
{{org.apache.logging.
[
https://issues.apache.org/jira/browse/LOG4J2-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137481#comment-16137481
]
ASF subversion and git services commented on LOG4J2-2009:
-
Commit
> On Aug 23, 2017, at 2:22, Gary Gregory wrote:
>
>> On Tue, Aug 22, 2017 at 10:27 AM, Remko Popma wrote:
>>
>> What I don't like about this proposal is that LogManager.getLogger(Class)
>> would end up working differently than
>> o.a.l.l.core.LoggerContext.getLogger(Class). (One uses Class.get
[
https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137356#comment-16137356
]
Ralph Goers commented on LOG4J2-2013:
-
Can you elaborate on the compatibility problem
[
https://issues.apache.org/jira/browse/LOG4J2-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137284#comment-16137284
]
Gary Gregory edited comment on LOG4J2-2005 at 8/22/17 8:04 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137284#comment-16137284
]
Gary Gregory commented on LOG4J2-2005:
--
Hm..., to avoid breaking existing configs we
[
https://issues.apache.org/jira/browse/LOG4J2-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137278#comment-16137278
]
Gary Gregory commented on LOG4J2-2000:
--
All of the levels in
{{https://developer.op
[
https://issues.apache.org/jira/browse/LOG4J2-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137269#comment-16137269
]
Gary Gregory commented on LOG4J2-2005:
--
The kind of fix will break existing configur
[
https://issues.apache.org/jira/browse/LOG4J2-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137201#comment-16137201
]
Taylor Patton commented on LOG4J2-2013:
---
I had some issues where the app I was test
“Out of bounds” is not the correct statement. Unnecessary is. We already
convert the class name to a String in the API so there is no reason to have
that method.
Ralph
> On Aug 22, 2017, at 8:32 AM, Gary Gregory wrote:
>
> Hi Ralph,
>
> I looked over the links and I (still) do understand th
LoggerContext is included in log4j-api as an SPI class. It's for
implementors, not users.
On 22 August 2017 at 12:22, Gary Gregory wrote:
> On Tue, Aug 22, 2017 at 10:27 AM, Remko Popma
> wrote:
>
> > What I don't like about this proposal is that LogManager.getLogger(Class)
> > would end up wor
[
https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137094#comment-16137094
]
Ralph Goers commented on LOG4J2-1925:
-
I have submitted a bug report with Oracle. Wai
On Tue, Aug 22, 2017 at 10:27 AM, Remko Popma wrote:
> What I don't like about this proposal is that LogManager.getLogger(Class)
> would end up working differently than
> o.a.l.l.core.LoggerContext.getLogger(Class). (One uses Class.getName, the
> other Class.getCanonicalName.)
>
No it would not,
[
https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137072#comment-16137072
]
Ralph Goers edited comment on LOG4J2-1925 at 8/22/17 5:17 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1925.
-
Resolution: Fixed
I have created a test project at https://github.com/rgoers/LOG4J2-1925 without
What I don't like about this proposal is that LogManager.getLogger(Class)
would end up working differently than
o.a.l.l.core.LoggerContext.getLogger(Class). (One uses Class.getName, the
other Class.getCanonicalName.)
Why not just use org.apache.logging.log4j.core.
LoggerContext.getLogger(clazz.get
[
https://issues.apache.org/jira/browse/LOG4NET-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137011#comment-16137011
]
Dominik Psenner commented on LOG4NET-572:
-
This leaves the question how we organi
[
https://issues.apache.org/jira/browse/LOG4NET-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137009#comment-16137009
]
Dominik Psenner commented on LOG4NET-572:
-
We might be able to parse the visual s
Github user chlowell closed the pull request at:
https://github.com/apache/logging-log4net/pull/14
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
Hi Ralph,
I looked over the links and I (still) do understand the separation and I
have a follow up question below.
First, to be precise, I am proposing to add this shorthand method (note
there is no @Override to ease compatibility, so no change to
org.apache.logging.log4j.spi.LoggerContext):
di
[
https://issues.apache.org/jira/browse/LOG4NET-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136788#comment-16136788
]
Dominik Psenner commented on LOG4NET-572:
-
Current state:
*
[build#6|https://bui
[
https://issues.apache.org/jira/browse/LOG4NET-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner reassigned LOG4NET-567:
---
Assignee: Dominik Psenner
> Use new csproj format to target multiple frameworks
> --
[
https://issues.apache.org/jira/browse/LOG4NET-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner updated LOG4NET-572:
Description: Currently all work done so far is available in branch
feature/netstandard-2.0;
[
https://issues.apache.org/jira/browse/LOG4NET-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136781#comment-16136781
]
ASF GitHub Bot commented on LOG4NET-572:
Github user dpsenner commented on the is
Github user dpsenner commented on the issue:
https://github.com/apache/logging-log4net/pull/14
Alright, let's move further discussion to JIRA
([LOG4NET-572](https://issues.apache.org/jira/browse/LOG4NET-572),
[LOG4NET-567](https://issues.apache.org/jira/browse/LOG4NET-567)). I would h
Dominik Psenner created LOG4NET-572:
---
Summary: Add target for netstandard-2.0
Key: LOG4NET-572
URL: https://issues.apache.org/jira/browse/LOG4NET-572
Project: Log4net
Issue Type: New Featur
31 matches
Mail list logo
