[
https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-519:
---
Attachment: (was: Generate.java)
Custom/Extended Loggers
---
[
https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-519:
---
Attachment: Generate.java
Generate_old_20140130.java
I've updated the attached
[
https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-519:
---
Description:
Please try out the attached [^Generate.java] tool that provides the
functionality
[
https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917362#comment-13917362
]
Remko Popma commented on LOG4J2-555:
With hindsight I probably saw the
[
https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917378#comment-13917378
]
vibin commented on LOG4J2-519:
--
Thanks,I tried test again with latest generated code, it
[
https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917398#comment-13917398
]
Gary Gregory commented on LOG4J2-555:
-
methods 3 or 4 lines: no opportunity for
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917415#comment-13917415
]
Bruce Brouwer commented on LOG4J2-547:
--
So, I've been thinking about the actual use
[
https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917419#comment-13917419
]
Remko Popma commented on LOG4J2-555:
I keep thinking there must be a more robust way
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917415#comment-13917415
]
Bruce Brouwer edited comment on LOG4J2-547 at 3/2/14 5:01 PM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917415#comment-13917415
]
Bruce Brouwer edited comment on LOG4J2-547 at 3/2/14 5:02 PM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917500#comment-13917500
]
Gary Gregory commented on LOG4J2-547:
-
This streaming aspect of Log4j2 really looks
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917561#comment-13917561
]
Matt Sicker commented on LOG4J2-547:
I'm starting to see two ways this can go: as part
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917561#comment-13917561
]
Matt Sicker edited comment on LOG4J2-547 at 3/2/14 9:16 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917565#comment-13917565
]
Bruce Brouwer commented on LOG4J2-547:
--
Matt, you're going down the exact same
[
https://issues.apache.org/jira/browse/LOG4J2-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917569#comment-13917569
]
Remko Popma commented on LOG4J2-555:
Hey Gary! I missed your comment. Yeah, I know!
org.apache.logging.log4j.core.AbstractServer
1. It's not abstract.
2. As it's not abstract, there are no abstract methods or any common
interface really.
That being said, would it make more sense for this to be an interface with
a simple log(LogEvent) method defined? Perhaps calling this class
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917570#comment-13917570
]
Matt Sicker commented on LOG4J2-547:
Considering the OSGi support tends to introduce
While it is not truly abstract it does act as the base class for
AbstractJMSReceiver (which JMSQueueReceiver and JMSTopicReceiver both extend),
SocketServer, and UDPSocketServer. On its own, AbstractServer doesn’t really
do anything. But they all end up calling the log method, which is really
Alright, I know I've brought this up a couple times, but this is also based
on new information I've learned about the esoteric rules behind versioning
in OSGi (which I'm pretty sure also applies to Maven; however, most people
don't use version number ranges in Maven dependencies).
Here's
Matt Sicker created LOG4J2-556:
--
Summary: Unnecessary dependency in log4j-api.
Key: LOG4J2-556
URL: https://issues.apache.org/jira/browse/LOG4J2-556
Project: Log4j 2
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LOG4J2-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-556:
---
Attachment: 0001-Remove-commons-httpclient-from-dependencies.patch
Unnecessary dependency in
How about something like LogListener or LogEventListener? It definitely
follows the pattern to be a listener class.
On 2 March 2014 15:55, Ralph Goers ralph.go...@dslextreme.com wrote:
While it is not truly abstract it does act as the base class for
AbstractJMSReceiver (which JMSQueueReceiver
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917602#comment-13917602
]
Gary Gregory commented on LOG4J2-547:
-
Please, not another jar.
Update LoggerStream
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917603#comment-13917603
]
Matt Sicker commented on LOG4J2-547:
For the streaming interface? Sure, it makes sense
[
https://issues.apache.org/jira/browse/LOG4J2-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-557:
---
Attachment: 0001-Add-gradle-build-info.patch
Add info for Gradle users on Maven Artifacts page
Matt Sicker created LOG4J2-557:
--
Summary: Add info for Gradle users on Maven Artifacts page
Key: LOG4J2-557
URL: https://issues.apache.org/jira/browse/LOG4J2-557
Project: Log4j 2
Issue Type:
[
https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917621#comment-13917621
]
Matt Sicker commented on LOG4J2-346:
Shouldn't the module names match the artefact
[
https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917622#comment-13917622
]
Matt Sicker commented on LOG4J2-543:
This is definitely a 2.1 or beyond feature. Even
[
https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-543.
Resolution: Later
Add JDO database appender
-
Key:
[
https://issues.apache.org/jira/browse/LOG4J2-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917637#comment-13917637
]
Matt Sicker commented on LOG4J2-238:
Adding to epic.
OSGi dependency failures in
To clarify, whatever we decide on the OSGi version number string *only* affects
the value for an OSGi-specific attribute in the manifest, right? (Not sure if
this attribute exists in the manifest for all jar files or only for the OSGi
ones.)
So it doesn't affect the jar/zip file names.
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917644#comment-13917644
]
Bruce Brouwer commented on LOG4J2-547:
--
If we were going to put the streaming
[
https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917643#comment-13917643
]
Remko Popma commented on LOG4J2-543:
Just FYI, usually I would prefer to leave the
[
https://issues.apache.org/jira/browse/LOG4J2-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917647#comment-13917647
]
Matt Sicker commented on LOG4J2-18:
---
So, uh, is this still a valid issue now that
Right. You can specify this all as metadata. It's easier to use the same
version number as the Maven artefacts, but it doesn't have to be the same
at all.
On 2 March 2014 18:16, Remko Popma remko.po...@gmail.com wrote:
To clarify, whatever we decide on the OSGi version number string *only*
[
https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917649#comment-13917649
]
Matt Sicker commented on LOG4J2-543:
Unless it's cool to add new appenders in 2.0.x, I
[
https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917652#comment-13917652
]
Remko Popma commented on LOG4J2-346:
It's probably best to aim to match OSGi users
In that case I'd be fine with 2.0.0.RELEASE for the reasons you mentioned.
Sent from my iPhone
On 2014/03/03, at 9:35, Matt Sicker boa...@gmail.com wrote:
Right. You can specify this all as metadata. It's easier to use the same
version number as the Maven artefacts, but it doesn't have to
[
https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917653#comment-13917653
]
Remko Popma commented on LOG4J2-543:
Unless adding something would somehow break
On Sun, Mar 2, 2014 at 7:49 PM, Remko Popma remko.po...@gmail.com wrote:
In that case I'd be fine with 2.0.0.RELEASE for the reasons you mentioned.
This is only for OSGi right? I'd hate to have to use that as Maven coords.
Gary
Sent from my iPhone
On 2014/03/03, at 9:35, Matt Sicker
Bruce Brouwer created LOG4J2-558:
Summary: Create a log4j-bom
Key: LOG4J2-558
URL: https://issues.apache.org/jira/browse/LOG4J2-558
Project: Log4j 2
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917662#comment-13917662
]
Gary Gregory commented on LOG4J2-547:
-
This clearly belongs in the api and/or core,
[
https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917663#comment-13917663
]
Gary Gregory commented on LOG4J2-543:
-
Another aspect to consider is whether
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917664#comment-13917664
]
Bruce Brouwer commented on LOG4J2-547:
--
Yes, the default search in search.maven.org
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917668#comment-13917668
]
Gary Gregory commented on LOG4J2-547:
-
Telling people they have to search some website
Fine by me. If you have gotten your account set up go ahead and make the change.
Sent from my iPad
On Mar 2, 2014, at 2:01 PM, Matt Sicker boa...@gmail.com wrote:
How about something like LogListener or LogEventListener? It definitely
follows the pattern to be a listener class.
On 2
[
https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917670#comment-13917670
]
Gary Gregory commented on LOG4J2-519:
-
[~rem...@yahoo.com] Why don't you commit the
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917673#comment-13917673
]
Bruce Brouwer commented on LOG4J2-547:
--
It sounds like the log4j team supports
Maven treats 2.0 or 2.0.0 very differently than 2.0.0-rc1. The first is
treated as numeric coordinates while the second is just a string. Once we
release 2.0 it is unlikely we would have another release with a string in it
until perhaps 3.0.
I would not recommend or be in favor of using
[
https://issues.apache.org/jira/browse/LOG4J2-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917690#comment-13917690
]
Matt Sicker commented on LOG4J2-543:
Well, I'm pretty sure that implementing a JDO
I don't believe I've received any follow-up yet on the account.
On 2 March 2014 19:30, Ralph Goers rgo...@apache.org wrote:
Fine by me. If you have gotten your account set up go ahead and make the
change.
Sent from my iPad
On Mar 2, 2014, at 2:01 PM, Matt Sicker boa...@gmail.com wrote:
[
https://issues.apache.org/jira/browse/LOG4J2-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-557:
---
Attachment: gradle-docs.diff
I ran {{patch -p1 0001-whatever.patch}} in a subversion checkout, then
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917712#comment-13917712
]
Bruce Brouwer commented on LOG4J2-547:
--
Ok, I need a bit of advice. In LogManager, I
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917734#comment-13917734
]
Remko Popma commented on LOG4J2-547:
If you need AbstractLogger functionality that is
Hi,
it is my pleasure to announce to the community
that Matt Sicker has joined our ranks.
He made remarkable contributions to LOG4J
and we all believe he is a valuable member
of Apache Logging Services now and in future.
Kind regards,
Dominik Psenner
55 matches
Mail list logo
