[jira] [Resolved] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

2017-05-26 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1911. - Resolution: Fixed I have changed the documentation of the DynamicThresholdFilter to add "If the

[jira] [Commented] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

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

[jira] [Comment Edited] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

2017-05-26 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027294#comment-16027294 ] Ralph Goers edited comment on LOG4J2-1911 at 5/27/17 6:43 AM: -

[jira] [Updated] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

2017-05-26 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1911: Issue Type: Documentation (was: Bug) > DynamicThresholdFilter defaultThreshold is not used to comp

[jira] [Assigned] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

2017-05-26 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1911: --- Assignee: Ralph Goers > DynamicThresholdFilter defaultThreshold is not used to compare again

[jira] [Commented] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

2017-05-26 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027294#comment-16027294 ] Ralph Goers commented on LOG4J2-1911: - I was able to add a test case that shows the p

[jira] [Comment Edited] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

2017-05-26 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027294#comment-16027294 ] Ralph Goers edited comment on LOG4J2-1911 at 5/27/17 6:37 AM: -

[jira] [Commented] (LOG4J2-1911) DynamicThresholdFilter defaultThreshold is not used to compare against event's level when there's no matching key found.

2017-05-26 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027123#comment-16027123 ] Gary Gregory commented on LOG4J2-1911: -- Hi Jerry, I do not see a patch or a PR. You

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

2017-05-26 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027117#comment-16027117 ] Gary Gregory commented on LOG4J2-1921: -- Can you try one of the {{org.apache.logging.

[jira] [Updated] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

2017-05-26 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1921: - Description: Hi, I integrated the log4j with my Android application and did the initial config.

Re: [log4net] Remove log4net github repo?

2017-05-26 Thread Stefan Bodewig
On 2017-05-25, Dominik Psenner wrote: > While applying the pull requests I stumbled upon pr/22 which is based on > the branch log4net-1.2.x. That branch has a lot of modifications but I am > unsure whether or not those changes have been merged into trunk or if there > has been a release made from

[jira] [Commented] (LOG4J2-1901) Fix travis-ci build

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

[GitHub] logging-log4j2 issue #79: LOG4J2-1901: Fix travis-ci build

2017-05-26 Thread mikaelstaldal
Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/79 It may be due to macros. When using Scala macros, you need to compile the macro definitions separately from whatever using the macros. If src/main and src/test are compiled together, it

[jira] [Commented] (LOG4J2-1901) Fix travis-ci build

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

[GitHub] logging-log4j2 issue #79: LOG4J2-1901: Fix travis-ci build

2017-05-26 Thread jvz
Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/79 Not finding the `Logger$` class sounds like the Scala code isn't being compiled properly. That's the companion object class name. --- If your project is set up for it, you can reply to this email

Re: Travis CI

2017-05-26 Thread Mikael Ståldal
I have seen Jenkins being used for testing PRs on GitHub. On 2017-05-26 17:17, Matt Sicker wrote: Travis is set up for testing pull requests and potentially other free GitHub-integrated services like coveralls, though if we looked into it, I bet we could do all those things strictly with Jenkins

Re: Travis CI

2017-05-26 Thread Matt Sicker
Travis is set up for testing pull requests and potentially other free GitHub-integrated services like coveralls, though if we looked into it, I bet we could do all those things strictly with Jenkins somehow. On 26 May 2017 at 06:27, Mikael Ståldal wrote: > Link to Travis CI build: > > https://tr

[jira] [Created] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

2017-05-26 Thread Ajitha (JIRA)
Ajitha created LOG4J2-1921: -- Summary: Getting ClassCastException while getting LoggerContext Key: LOG4J2-1921 URL: https://issues.apache.org/jira/browse/LOG4J2-1921 Project: Log4j 2 Issue Type: Bug

Re: Travis CI

2017-05-26 Thread Mikael Ståldal
Link to Travis CI build: https://travis-ci.org/apache/logging-log4j2/builds/236303848?utm_source=github_status&utm_medium=notification On 2017-05-26 13:20, Mikael Ståldal wrote: Now the Travis CI build almost works, but fails with: - The log length has exceeded the limit of 4 MB (this usua

[GitHub] logging-log4j2 pull request #80: Testing Travis CI

2017-05-26 Thread mikaelstaldal
Github user mikaelstaldal closed the pull request at: https://github.com/apache/logging-log4j2/pull/80 --- 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 f

Travis CI

2017-05-26 Thread Mikael Ståldal
Now the Travis CI build almost works, but fails with: - The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over). The job has been terminated - After 49 minutes. Why do we even use Travis CI when we have Jenkins

[GitHub] logging-log4j2 pull request #80: Testing Travis CI

2017-05-26 Thread mikaelstaldal
GitHub user mikaelstaldal opened a pull request: https://github.com/apache/logging-log4j2/pull/80 Testing Travis CI This is only a test for Travis CI. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/logging-log4j2 travis-te

[jira] [Commented] (LOG4J2-1901) Fix travis-ci build

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

[jira] [Commented] (LOG4J2-1901) Fix travis-ci build

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

[GitHub] logging-log4j2 pull request #79: LOG4J2-1901: Fix travis-ci build

2017-05-26 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/79 --- 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] [Commented] (LOG4J2-1901) Fix travis-ci build

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

[GitHub] logging-log4j2 issue #79: LOG4J2-1901: Fix travis-ci build

2017-05-26 Thread mikaelstaldal
Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/79 That's strange. However, the Scala modules will soon be remove from this repository (as they live in the logging-log4j-scala repo). So maybe we should not spend time on fixing that probl