[jira] [Commented] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985818#comment-15985818 ] Gary Gregory commented on LOG4J2-1891: -- Tapan, JIRA is not a support forum, please

[jira] [Commented] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Tapan Choudhury (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985810#comment-15985810 ] Tapan Choudhury commented on LOG4J2-1891: - I have other queries, for which should

[jira] [Commented] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Tapan Choudhury (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985808#comment-15985808 ] Tapan Choudhury commented on LOG4J2-1891: - I am able to resolve the issue. There

[jira] [Commented] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985804#comment-15985804 ] Matt Sicker commented on LOG4J2-1891: - Otherwise, your code looks fine as far as I ca

[jira] [Commented] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985797#comment-15985797 ] Matt Sicker commented on LOG4J2-1891: - Based on the code you attached, the config sho

[jira] [Updated] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Tapan Choudhury (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapan Choudhury updated LOG4J2-1891: Attachment: Log4j2Plugins.dat First I build with IDE and then tried with maven command line

[jira] [Commented] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985624#comment-15985624 ] Matt Sicker commented on LOG4J2-1891: - How are you building this? Via Maven/Gradle/so

[jira] [Updated] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Tapan Choudhury (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapan Choudhury updated LOG4J2-1891: Attachment: Logfile.log RecordCountBasedTriggeringPolicy.java As requested.

[jira] [Commented] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985587#comment-15985587 ] Ralph Goers commented on LOG4J2-1891: - I would suggest you attach your plugin and the

[jira] [Updated] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Tapan Choudhury (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapan Choudhury updated LOG4J2-1891: Description: I want log files to be rolled over on every 2 log entries. For this, I am

[jira] [Created] (LOG4J2-1891) Creating Custom TriggeringPolicy

2017-04-26 Thread Tapan Choudhury (JIRA)
Tapan Choudhury created LOG4J2-1891: --- Summary: Creating Custom TriggeringPolicy Key: LOG4J2-1891 URL: https://issues.apache.org/jira/browse/LOG4J2-1891 Project: Log4j 2 Issue Type: Question

[jira] [Commented] (LOG4J2-1890) log4j2.properties: logger not correctly initalized if level has trailing space

2017-04-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985259#comment-15985259 ] ASF GitHub Bot commented on LOG4J2-1890: Github user thuri commented on the issue

Re: [log4net] [Discuss] migration to git

2017-04-26 Thread Kamal Mettananda
+1 --- Kamal Mettananda www.digizol.com On Sat, Apr 15, 2017 at 10:00 PM, Harry Martyrossian wrote: > +1 > > -Original Message- > From: Matt Sicker [mailto:boa...@gmail.com] > Sent: Friday, April 14, 2017 8:03 AM > To: dev@logging.apache.org > Subjec

[GitHub] logging-log4j2 issue #75: trim levels read from properties file to remove tr...

2017-04-26 Thread thuri
Github user thuri commented on the issue: https://github.com/apache/logging-log4j2/pull/75 Du bist auch überall ;-) Danke für den Issue Am 26. April 2017 19:49:52 MESZ schrieb Pascal Schumacher : >I guess there should be a jira issue for this, so I created >https://i

[jira] [Commented] (LOG4J2-1890) log4j2.properties: logger not correctly initalized if level has trailing space

2017-04-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985251#comment-15985251 ] ASF GitHub Bot commented on LOG4J2-1890: Github user PascalSchumacher commented o

[GitHub] logging-log4j2 issue #75: trim levels read from properties file to remove tr...

2017-04-26 Thread PascalSchumacher
Github user PascalSchumacher commented on the issue: https://github.com/apache/logging-log4j2/pull/75 I guess there should be a jira issue for this, so I created https://issues.apache.org/jira/browse/LOG4J2-1890 --- If your project is set up for it, you can reply to this email and ha

[jira] [Created] (LOG4J2-1890) log4j2.properties: logger not correctly initalized if level has trailing space

2017-04-26 Thread Pascal Schumacher (JIRA)
Pascal Schumacher created LOG4J2-1890: - Summary: log4j2.properties: logger not correctly initalized if level has trailing space Key: LOG4J2-1890 URL: https://issues.apache.org/jira/browse/LOG4J2-1890

Re: [log4j] Log4j Java 9 support has been added

2017-04-26 Thread Ralph Goers
Sure you can. In the project settings select the module. You can change it there. Ralph > On Apr 26, 2017, at 7:35 AM, Mikael Ståldal wrote: > > I don't think you can specify different JDK:s for different modules with > IntelliJ. You can specify different source and target levels, but that > d

Re: [log4j] Log4j Java 9 support has been added

2017-04-26 Thread Mikael Ståldal
I don't think you can specify different JDK:s for different modules with IntelliJ. You can specify different source and target levels, but that doesn't help here. Even though I set log4j-perf to 1.7, I get that error. On Wed, Apr 26, 2017 at 4:13 PM, Ralph Goers wrote: > You could compile the ap

Re: [log4j] Log4j Java 9 support has been added

2017-04-26 Thread Ralph Goers
You could compile the api module with Java 9 and the rest with Java 7. Until the module-info.java files are added the api module is the only thing that has Java 9 code in it. Ralph > On Apr 26, 2017, at 6:55 AM, Mikael Ståldal wrote: > > I was able to get log4j-api to build by manually instal

Re: [log4j] Log4j Java 9 support has been added

2017-04-26 Thread Mikael Ståldal
I was able to get log4j-api to build by manually installing JDK 9 and setting JDK 9 for that module. But now it fails in log4j-perf with the error below. Maybe related to https://bugs.openjdk.java.net/browse/JDK-8152842 Error:java: Annotation generator had thrown the exception. java.lang.NoClassD

Re: [log4j] Log4j Java 9 support has been added

2017-04-26 Thread Apache
You could try using java 9 Sent from my iPad > On Apr 26, 2017, at 2:20 AM, Mikael Ståldal wrote: > > Now I cannot build the project in IntelliJ IDEA anymore. It complains that > lambda expressions are not supported in Java 7 in StackWalkerStackLocator. > > Any suggestions? > > On Fri, Apr 21

[jira] [Commented] (LOG4J2-1854) Gelf TCP endpoint

2017-04-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984604#comment-15984604 ] ASF GitHub Bot commented on LOG4J2-1854: Github user xjodoin closed the pull requ

[GitHub] logging-log4j2 pull request #67: LOG4J2-1854 - Add new parameter to include ...

2017-04-26 Thread xjodoin
Github user xjodoin closed the pull request at: https://github.com/apache/logging-log4j2/pull/67 --- 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 feature

[jira] [Updated] (LOG4J2-1854) Gelf TCP endpoint

2017-04-26 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1854: --- Issue Type: Improvement (was: Bug) > Gelf TCP endpoint > -- > >

[jira] [Commented] (LOG4J2-1854) Gelf TCP endpoint

2017-04-26 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984485#comment-15984485 ] Mikael Ståldal commented on LOG4J2-1854: "Fixed" the no compression issue by impr

[jira] [Resolved] (LOG4J2-1854) Gelf TCP endpoint

2017-04-26 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1854. Resolution: Fixed Fix Version/s: 2.9 In Git master. Tested with Graylog 2.2.3 GELP

[jira] [Assigned] (LOG4J2-1854) Gelf TCP endpoint

2017-04-26 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1854: -- Assignee: Mikael Ståldal > Gelf TCP endpoint > -- > >

[jira] [Commented] (LOG4J2-1854) Gelf TCP endpoint

2017-04-26 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984481#comment-15984481 ] ASF subversion and git services commented on LOG4J2-1854: - Commit

[jira] [Commented] (LOG4J2-1854) Gelf TCP endpoint

2017-04-26 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984477#comment-15984477 ] ASF GitHub Bot commented on LOG4J2-1854: Github user mikaelstaldal commented on t

[GitHub] logging-log4j2 issue #67: LOG4J2-1854 - Add new parameter to include tcp Gel...

2017-04-26 Thread mikaelstaldal
Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/67 I have fixed this in master branch, this PR can be closed. --- 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

Re: [log4j] Log4j Java 9 support has been added

2017-04-26 Thread Mikael Ståldal
Now I cannot build the project in IntelliJ IDEA anymore. It complains that lambda expressions are not supported in Java 7 in StackWalkerStackLocator. Any suggestions? On Fri, Apr 21, 2017 at 10:59 AM, Mikael Ståldal wrote: > Should the vendor of the Java 7, 8 and 9 toolchains be "sun"? Shouldn'