Re: [14/14] logging-log4j2 git commit: Update BOM

I created a new git repo for log4j2-tools. We should not create any more modules if we can avoid it. Ralph > On Apr 10, 2017, at 7:28 AM, Remko Popma wrote: > > I guess this is a matter of preference but we already have a lot of modules. > Having one for all standalone

[jira] [Commented] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

[ https://issues.apache.org/jira/browse/LOG4J2-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963050#comment-15963050 ] Gary Gregory commented on LOG4J2-1873: -- ICU4J might have something we can optionally depend on or

Re: [14/14] logging-log4j2 git commit: Update BOM

Yes, that is the repo. Initially, all it needs is a parent pom that references the module you created. We can move other stuff in later. It will need a web site of some kind but we can also worry about that later. Ralph > On Apr 10, 2017, at 9:11 AM, Mikael Ståldal

Re: [14/14] logging-log4j2 git commit: Update BOM

The whole point of this is to get the server components out of log4j-core, so we need to create a new module. Maybe this new module can be moved to log4j2-tools repo. On Mon, Apr 10, 2017 at 5:48 PM, Ralph Goers wrote: > I created a new git repo for log4j2-tools. We

Re: [14/14] logging-log4j2 git commit: Update BOM

Is this where a Chainsaw refresh would live? Gary On Apr 10, 2017 9:01 AM, "Ralph Goers" wrote: > I’m fine with that. I just don’t want more modules in the main project. > > Ralph > > On Apr 10, 2017, at 8:56 AM, Mikael Ståldal > wrote: >

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963043#comment-15963043 ] Gary Gregory commented on LOG4J2-1864: -- The old factory method does not come into play if you remove

Re: [14/14] logging-log4j2 git commit: Update BOM

Maybe, but if it is large enough I would just migrate it from svn to its own git repo. Ralph > On Apr 10, 2017, at 9:05 AM, Gary Gregory wrote: > > Is this where a Chainsaw refresh would live? > > Gary > > On Apr 10, 2017 9:01 AM, "Ralph Goers"

Re: [14/14] logging-log4j2 git commit: Update BOM

I’m fine with that. I just don’t want more modules in the main project. Ralph > On Apr 10, 2017, at 8:56 AM, Mikael Ståldal wrote: > > The whole point of this is to get the server components out of log4j-core, so > we need to create a new module. Maybe this new

Re: [14/14] logging-log4j2 git commit: Update BOM

Is it this repo? git://git.apache.org/logging-log4j-tools.git It is currently empty (except two text files). I don't feel confident to do the initial setup of the repository. On Mon, Apr 10, 2017 at 5:48 PM, Ralph Goers wrote: > I created a new git repo for

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962487#comment-15962487 ] ASF GitHub Bot commented on LOG4J2-1864: Github user codescale commented on a diff in the pull

[jira] [Created] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

Roman Leventov created LOG4J2-1873: -- Summary: Implement UTF-8 encoding that doesn't use CharsetEncoder Key: LOG4J2-1873 URL: https://issues.apache.org/jira/browse/LOG4J2-1873 Project: Log4j 2

[jira] [Commented] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

[ https://issues.apache.org/jira/browse/LOG4J2-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962650#comment-15962650 ] Roman Leventov commented on LOG4J2-1873: [~rem...@yahoo.com] Yes, I think it would be something

Re: Failed tests

These two tests fail on Java 8 (at least on Linux). They work on Java 7 (that's why the Jenkins build doesn't fail). On Mon, Apr 10, 2017 at 11:32 AM, Mikael Ståldal wrote: > I get these test failures on master branch: > > Failed tests: >

Module for server components

OK to merge branch LOG4J2-1851 to master? https://issues.apache.org/jira/browse/LOG4J2-1851 -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential

[jira] [Commented] (LOG4J2-1872) Update JavaMail from 1.5.5 to 1.5.6

[ https://issues.apache.org/jira/browse/LOG4J2-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962613#comment-15962613 ] ASF subversion and git services commented on LOG4J2-1872: - Commit

[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962611#comment-15962611 ] ASF subversion and git services commented on LOG4J2-1869: - Commit

[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962612#comment-15962612 ] ASF subversion and git services commented on LOG4J2-1869: - Commit

[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module

[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962615#comment-15962615 ] ASF subversion and git services commented on LOG4J2-1851: - Commit

[jira] [Commented] (LOG4J2-1868) Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0

[ https://issues.apache.org/jira/browse/LOG4J2-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962610#comment-15962610 ] ASF subversion and git services commented on LOG4J2-1868: - Commit

[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962614#comment-15962614 ] ASF subversion and git services commented on LOG4J2-1860: - Commit

Failed tests

I get these test failures on master branch: Failed tests: SecureSocketAppenderSocketOptionsTest.testSocketOptions:112 expected:<2> but was:<0> SocketAppenderSocketOptionsTest.testSocketOptions:92 expected:<2> but was:<0> -- [image: MagineTV] *Mikael Ståldal* Senior software developer

[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962602#comment-15962602 ] ASF subversion and git services commented on LOG4J2-1860: - Commit

[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962599#comment-15962599 ] ASF subversion and git services commented on LOG4J2-1869: - Commit

[jira] [Commented] (LOG4J2-1869) Update Kafka client from 0.10.1.1 to 0.10.2.0

[ https://issues.apache.org/jira/browse/LOG4J2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962600#comment-15962600 ] ASF subversion and git services commented on LOG4J2-1869: - Commit

[jira] [Commented] (LOG4J2-1872) Update JavaMail from 1.5.5 to 1.5.6

[ https://issues.apache.org/jira/browse/LOG4J2-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962601#comment-15962601 ] ASF subversion and git services commented on LOG4J2-1872: - Commit

[jira] [Commented] (LOG4J2-1868) Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0

[ https://issues.apache.org/jira/browse/LOG4J2-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962598#comment-15962598 ] ASF subversion and git services commented on LOG4J2-1868: - Commit

Re: Failed tests

I've always seen strange error logs in the socket tests, though they've always passed for me. On 10 April 2017 at 04:59, Mikael Ståldal wrote: > These two tests fail on Java 8 (at least on Linux). They work on Java 7 > (that's why the Jenkins build doesn't fail). > >

Re: Module for server components

Yeah, I think we're ready to work toward 2.9 now. On 10 April 2017 at 05:28, Mikael Ståldal wrote: > OK to merge branch LOG4J2-1851 to master? > > https://issues.apache.org/jira/browse/LOG4J2-1851 > > -- > [image: MagineTV] > > *Mikael Ståldal* > Senior software

[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module

[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962912#comment-15962912 ] ASF subversion and git services commented on LOG4J2-1851: - Commit

[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module

[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962911#comment-15962911 ] ASF subversion and git services commented on LOG4J2-1851: - Commit

[jira] [Resolved] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module

[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1851. Resolution: Fixed Fix Version/s: 2.9 In Git master > Move

Re: Failed tests

Maybe Gary can have a look? According to Git history, he added those tests. On Mon, Apr 10, 2017 at 4:06 PM, Matt Sicker wrote: > I've always seen strange error logs in the socket tests, though they've > always passed for me. > > On 10 April 2017 at 04:59, Mikael Ståldal

Re: [14/14] logging-log4j2 git commit: Update BOM

Wouldn't it be better to have one for server and another for the other tools? On Mon, Apr 10, 2017 at 4:23 PM, Remko Popma wrote: > I thought we were going to name this module log4j-tools instead of > log4j-server, so it can host all our standalone apps? > > On Mon, Apr

[jira] [Commented] (LOG4J2-1851) Move org.apache.logging.log4j.core.net.server package to new module

[ https://issues.apache.org/jira/browse/LOG4J2-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962913#comment-15962913 ] ASF subversion and git services commented on LOG4J2-1851: - Commit

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962920#comment-15962920 ] ASF GitHub Bot commented on LOG4J2-1864: Github user jvz commented on a diff in the pull request:

[jira] [Commented] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

[ https://issues.apache.org/jira/browse/LOG4J2-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962930#comment-15962930 ] Matt Sicker commented on LOG4J2-1873: - I'd be interested in seeing this feature myself. The standard

Re: [14/14] logging-log4j2 git commit: Update BOM

I thought we were going to name this module log4j-tools instead of log4j-server, so it can host all our standalone apps? On Mon, Apr 10, 2017 at 11:11 PM, wrote: > Update BOM > > > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo > Commit:

Re: [14/14] logging-log4j2 git commit: Update BOM

I guess this is a matter of preference but we already have a lot of modules. Having one for all standalone applications makes it easier for our users to find things. On Mon, Apr 10, 2017 at 11:24 PM, Mikael Ståldal wrote: > Wouldn't it be better to have one for server

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #58

See Changes: [mikael.staldal] Move server components from core to new server module [mikael.staldal] Changelog

Jenkins build is back to normal : Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #58

See - To unsubscribe, e-mail:

[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962603#comment-15962603 ] ASF subversion and git services commented on LOG4J2-1860: - Commit

[jira] [Commented] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962604#comment-15962604 ] ASF subversion and git services commented on LOG4J2-1860: - Commit

[jira] [Resolved] (LOG4J2-1860) Shortcut to add Property and KeyValuePair component in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1860. Resolution: Fixed In Git master. > Shortcut to add Property and KeyValuePair component in

[jira] [Commented] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

[ https://issues.apache.org/jira/browse/LOG4J2-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962607#comment-15962607 ] Remko Popma commented on LOG4J2-1873: - I'm open to ideas. We did something similar with

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.7 (unlimited security) 64-bit Windows only #57

See Changes: [mikael.staldal] LOG4J2-1860 Shortcut to add Property and KeyValuePair component in [mikael.staldal] Update

Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited security) 64-bit Windows only #57

See Changes: [mikael.staldal] LOG4J2-1860 Shortcut to add Property and KeyValuePair component in [mikael.staldal] Update

[jira] [Commented] (LOG4J2-1873) Implement UTF-8 encoding that doesn't use CharsetEncoder

[ https://issues.apache.org/jira/browse/LOG4J2-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963846#comment-15963846 ] Roman Leventov commented on LOG4J2-1873: Or implementation from Apache Harmony: