The only reason to have more than the single vararg version is for
performance. I don't think the marker .add method is going to be called
often so ultra-performance is not necessary. I say don't bother with the
one or two param variant. I just want the varargs version.
On Tue, Apr 22, 2014 at 8:
It sounds reasonable to me to require a non-null name.
On Wed, Apr 23, 2014 at 10:17 AM, Matt Sicker wrote:
> There's no point in using a null-named Marker, right? Many methods don't
> allow for a null argument for Marker name, but the constructor does. I'm
> going to change this.
>
> --
> Matt
Yes, that's make it easier for the rest of us to understand what is going
on ;)
Gary
On Thu, Apr 24, 2014 at 7:40 PM, Ralph Goers wrote:
> Matt,
>
> Unless you are creating an issue to immediately fix a bug, can you please
> have the description state what the problem or issue is? You can then
Matt,
Unless you are creating an issue to immediately fix a bug, can you please have
the description state what the problem or issue is? You can then either add a
subsequent comment or start another paragraph in the description with a heading
of “Proposed Solution”. I like to be able to unders
Matt Sicker created LOG4J2-614:
--
Summary: Log4j API should allow specifying a LoggerContextFactory
at runtime.
Key: LOG4J2-614
URL: https://issues.apache.org/jira/browse/LOG4J2-614
Project: Log4j 2
Matt Sicker created LOG4J2-613:
--
Summary: log4j-core bundle specifies javax.servlet version range
[3.0,4)
Key: LOG4J2-613
URL: https://issues.apache.org/jira/browse/LOG4J2-613
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980177#comment-13980177
]
Ralph Goers commented on LOG4J2-611:
I see you opened an issue with hazelcast. I thin
[
https://issues.apache.org/jira/browse/LOG4J2-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1397#comment-1397
]
Mikael Ståldal commented on LOG4J2-611:
---
I don't like to be tied to SLF4J though, so
[
https://issues.apache.org/jira/browse/LOG4J2-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-611:
--
Priority: Minor (was: Major)
> Logj 1.2 emulation is not complete
> --
[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979390#comment-13979390
]
Abid edited comment on LOG4J2-461 at 4/24/14 7:32 AM:
--
Hi,
I am also
[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979390#comment-13979390
]
Abid edited comment on LOG4J2-461 at 4/24/14 7:32 AM:
--
Hi,
I am also
[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abid updated LOG4J2-461:
Attachment: MANIFEST.MF
> ERROR StatusLogger Unable to locate a logging implementation, using
> SimpleLogger
> --
[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979390#comment-13979390
]
Abid edited comment on LOG4J2-461 at 4/24/14 7:28 AM:
--
Hi,
I am also
[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979390#comment-13979390
]
Abid commented on LOG4J2-461:
-
Hi,
I am also hitting the same ClassCastException issue while
14 matches
Mail list logo
