[GitHub] logging-log4j2 pull request #73: Add a new LuceneAppender which writes loggi...

Github user liyuj closed the pull request at: https://github.com/apache/logging-log4j2/pull/73 --- 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 i

[GitHub] logging-log4j2 issue #73: Add a new LuceneAppender which writes logging even...

Github user liyuj commented on the issue: https://github.com/apache/logging-log4j2/pull/73 If so, I think it is more reasonable to put it in the log4j-nosql module. We rearrange the code and submit it again. --- If your project is set up for it, you can reply to this email and hav

[GitHub] logging-log4j2 issue #73: Add a new LuceneAppender which writes logging even...

Github user liyuj commented on the issue: https://github.com/apache/logging-log4j2/pull/73 If so, I think it is more reasonable to put it in the log4j-nosql module. We rearrange the code and submit it again. --- If your project is set up for it, you can reply to this email and hav

[jira] [Comment Edited] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976019#comment-15976019 ] chandra edited comment on LOG4J2-1883 at 4/20/17 3:53 AM: -- With

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976019#comment-15976019 ] chandra commented on LOG4J2-1883: - With all the discussion above, it is a good FYI on the

[GitHub] logging-log4j2 issue #73: Add a new LuceneAppender which writes logging even...

Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/73 This vaguely sounds like a log4j-nosql appender. I'd consider a similar one for Elasticsearch to fall under that module. --- If your project is set up for it, you can reply to this email and have

Re: Roadmap

I agree with Ralph that there are many environments that can't upgrade their Java version but still want to use the nice features Log4j2 offers. I've also worked in such environments. I would prefer to support older versions as long as possible. (What that means concretely is open for discussion

Re: PR#72 build failure.

Yeah. I believe you. was just wondering why the all build failures. ;) thanks, Chandra On 20 Apr 2017, 5:33 AM +0530, Matt Sicker , wrote: > Don't worry about the build failure. We can still merge it. :) > > On 19 April 2017 at 00:43, Chandra wrote: > > > Hi List, > > > > I had a minor update on

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975940#comment-15975940 ] Remko Popma commented on LOG4J2-1883: - Matt, sorry for the overlap. :-( I didn't see

Re: Roadmap

I just want a plan for when we upgrade. Log4j is such low level code that it's not a big deal to me for using Java 8 syntax. I'm mostly interested in supporting the v8 APIs, and Spring has an interesting way of doing that. On Wed, Apr 19, 2017 at 18:01, Ralph Goers wrote: > I can’t agree to that

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975936#comment-15975936 ] Remko Popma commented on LOG4J2-1883: - [~Anthony Maire] Thanks for the in-depth analy

Re: Roadmap

I can’t agree to that. See https://spring.io/blog/2015/04/01/ongoing-support-for-java-7-and-even-java-6 for Spring’s perspective on this. Log4j is such a fundamental framework that, while we need to support new featu

Re: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

The liquibase module is for setting up liquibase to use log4j2 (it has a strange logging configuration system). It doesn't log *to* anything specifically. I agree that the lucene one belongs with the nosql appenders, though I also think that each plugin that requires dependencies to function might

Re: Roadmap

Roadmap wise, I think dropping support for Java 7 when Java 9 comes out might make sense, though that also depends on where we are release-wise at the time. In the meantime, modularizing the core more and breaking into more subprojects may help find any desires for a semantically breaking change fo

Re: [Scala][VOTE] Release log4j-api-scala 11.0 rc1

It's the same maven build as log4j. Copying over the BUILDING.txt file would be a good idea, though. On 19 April 2017 at 11:52, Gary Gregory wrote: > Adding a BUILDING.txt to the root of the src zip would help. Especially, > since there might (or not) be some scalaness to the build. Can you post

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975771#comment-15975771 ] Matt Sicker commented on LOG4J2-1883: - This looks like a good opportunity to enhance

Re: PR#72 build failure.

Don't worry about the build failure. We can still merge it. :) On 19 April 2017 at 00:43, Chandra wrote: > Hi List, > > I had a minor update on the documentation for which I sent a pull request. > Not sure what happened but, the travis build failed. > I see a lot of build failures from the PRs,

Re: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

So you are one of those who think that NoSQL stands for No SQL. It doesn’t. It is an acronym for “Not Only SQL”, which means it can contain almost anything related to data stores. I could see us having a repo for transports, which would include things like the Flume Appender and a Netty Appe

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

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

Re: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

Yeah, I considered that... We could rename log4j-nosql to log4j-search. I've never liked "No*" names, it's like voting against a candidate, you're not saying anything about what you want. NoSQL, pft! ;-) Or we could put this new appender in a new -search module and put the liquibase stuff in there

Re: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

What other functionality could go into a potential log4j-lucene module? Is this really a category? We already have so many modules... I'd prefer to add this to one of the existing modules (nosql?) or create a more general module that we could lump other stuff in later. Sent from my iPhone >

[GitHub] logging-log4j2 issue #73: Add a new LuceneAppender which writes logging even...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/73 Can you please provide some JUnit tests? There are no tests ATM. Thank you, Gary --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] logging-log4j2 pull request #73: Add a new LuceneAppender which writes loggi...

Github user garydgregory commented on a diff in the pull request: https://github.com/apache/logging-log4j2/pull/73#discussion_r112268957 --- Diff: log4j-core/src/main/java/org/apache/logging/log4j/core/appender/lucene/LuceneAppender.java --- @@ -0,0 +1,295 @@ +/* + * Licen

Re: Roadmap

On Wed, Apr 19, 2017 at 10:23 AM, Ralph Goers wrote: > I have no idea what your versions are, but 2.9 is going to contain the > first support for Java 9, but it will continue to support Java 7. I am > assuming your numbering scheme is about what version ONLY supports a > particular Java release?

[GitHub] logging-log4j2 issue #73: Add a new LuceneAppender which writes logging even...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/73 Thank you for your patch! Can you please redo this work as a patch to provide a new module called "log4j-lucene"? This does not belong in our Core module and we do not have a home for thi

Re: Roadmap

I have no idea what your versions are, but 2.9 is going to contain the first support for Java 9, but it will continue to support Java 7. I am assuming your numbering scheme is about what version ONLY supports a particular Java release? I am not in favor of that. With semantic versioning the nu

Re: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

On Wed, Apr 19, 2017 at 10:11 AM, Ralph Goers wrote: > It should not go into the main log4j build. > Agreed. Gary > > Ralph > > > On Apr 19, 2017, at 9:43 AM, Gary Gregory > wrote: > > > > Should this should go into a new module log4j-lucene? > > > > Gary > > > > -- Forwarded message

Roadmap

Hi All, I like projects that have a road-map page. It can be vague or precise. But we should at least discuss it here. I am bringing this up partly in light of https://issues.apache.org/jira/browse/LOG4J2-1883 How about: v 2.x - Java 7 v 3.x - Java 8 v 4.x - Java 9 Is that too weird? I am not i

Re: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

It should not go into the main log4j build. Ralph > On Apr 19, 2017, at 9:43 AM, Gary Gregory wrote: > > Should this should go into a new module log4j-lucene? > > Gary > > -- Forwarded message -- > From: liyujue > Date: Wed, Apr 19, 2017 at 12:18 AM > Subject: [apache/logging

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975084#comment-15975084 ] Gary Gregory commented on LOG4J2-1807: -- Well, we do leave ourselves some wiggle room

Re: [Scala][VOTE] Release log4j-api-scala 11.0 rc1

Adding a BUILDING.txt to the root of the src zip would help. Especially, since there might (or not) be some scalaness to the build. Can you post build help here if you need more VOTEs? TY, Gary On Sat, Apr 15, 2017 at 10:53 AM, Matt Sicker wrote: > Hello all, this is the first release candidate

[jira] [Resolved] (LOG4J2-1877) Missing documentation for Max index limit in DefaultRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1877. -- Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.9 In git master; plea

[jira] [Commented] (LOG4J2-1877) Missing documentation for Max index limit in DefaultRolloverStrategy

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

Fwd: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73)

Should this should go into a new module log4j-lucene? Gary -- Forwarded message -- From: liyujue Date: Wed, Apr 19, 2017 at 12:18 AM Subject: [apache/logging-log4j2] Add a new LuceneAppender which writes logging events to a lucene index library. (#73) To: apache/logging-log4j2 C

[jira] [Closed] (LOG4J2-1733) Add SyncSend attribute to KafkaAppender (as in KafkaLog4jAppender)

[ https://issues.apache.org/jira/browse/LOG4J2-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1733. -- > Add SyncSend attribute to KafkaAppender (as in KafkaLog4jAppender) >

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974936#comment-15974936 ] Ralph Goers commented on LOG4J2-1883: - I am about to introduce a commit that requires

[jira] [Updated] (LOG4J2-1800) Errors when sending to Kafka with syncSend=false are not reported

[ https://issues.apache.org/jira/browse/LOG4J2-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1800: --- Fix Version/s: 2.8.1 > Errors when sending to Kafka with syncSend=false are not reported > --

[jira] [Closed] (LOG4J2-1800) Errors when sending to Kafka with syncSend=false are not reported

[ https://issues.apache.org/jira/browse/LOG4J2-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1800. -- > Errors when sending to Kafka with syncSend=false are not reported > -

[jira] [Commented] (LOG4J2-1807) [core] Add and implement LogEvent.toImmutable()

[ https://issues.apache.org/jira/browse/LOG4J2-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974933#comment-15974933 ] Mikael Ståldal commented on LOG4J2-1807: This is now released, and cannot be chan

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974930#comment-15974930 ] Anthony Maire commented on LOG4J2-1883: --- Hi Having this microsecond precision will

[jira] [Closed] (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 closed LOG4J2-1860. -- > Shortcut to add Property and KeyValuePair component in ConfigurationBuilder > ---

[jira] [Closed] (LOG4J2-1876) Unreliable checking for runtime dependencies

[ https://issues.apache.org/jira/browse/LOG4J2-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1876. -- > Unreliable checking for runtime dependencies > > >

[jira] [Closed] (LOG4J2-1880) Confusing configuration file discovery

[ https://issues.apache.org/jira/browse/LOG4J2-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1880. -- > Confusing configuration file discovery > -- > >

Re: [log4net] [VOTE] migrate log4net from svn to git

+1 You are right Gary. Apologies and thanks for pointing this out. I simply took the last release vote as a template for this vote and so this vote happened to become non-lazy. We already have enough +1s, so luckily this should not become an issue. :-) Dominik On 2017-04-18 17:33, Gary Gre

Re: Antwort: [Newsletter] Re: Log4net website issue

Regarding the consistency with other log4 projects, I as a .NET developer and log4net user, consider consistency with other .NET documentation (aka MSDN-Style) much more important then with let's say log4j. I don't think either that we should re-style the SDK reference. The issue we try to so

[jira] [Created] (LOG4NET-563) Site: make the site look like the site of other logging subprojects

Dominik Psenner created LOG4NET-563: --- Summary: Site: make the site look like the site of other logging subprojects Key: LOG4NET-563 URL: https://issues.apache.org/jira/browse/LOG4NET-563 Project: Lo

Antwort: [Newsletter] Re: Log4net website issue

Dominik Psenner wrote on 19.04.2017 10:40:17: > > I completely purged that mess from my memory. We need a solution that > just works and links to generated code are not "the solution"©. :-) When > I build log4net I get the following files: > > * log4net.dll > * log4net.pdb > * log4net.xml >

Re: Log4net website issue

Guten Tag Stefan Bodewig, am Mittwoch, 19. April 2017 um 10:13 schrieben Sie: > As log4net uses maven to build the site as well, this could probably > solved by using the same skin (I've never tried to fiddle with that, > though). As log4cxx has done the same by simply copying over templates and

Re: Log4net website issue

On 2017-04-19 10:13, Stefan Bodewig wrote: On 2017-04-19, Dominik Psenner wrote: From a higher perspective I would also like to see all logging subprojects to have one website style. Looking at the website of log4net and log4j those projects appear to be unrelated, whereas the log4cxx and log4

Re: [Scala][VOTE] Release log4j-api-scala 11.0 rc1

OK, then +1 On Tue, Apr 18, 2017 at 11:23 PM, Matt Sicker wrote: > I've had the opposite problem at work before where a jar published from SBT > wasn't giving transitive dependencies in Gradle. I blame Ivy. > > On Tue, Apr 18, 2017 at 02:25, Mikael Ståldal > wrote: > > > I just tested this, an

Re: Log4net website issue

I completely purged that mess from my memory. We need a solution that just works and links to generated code are not "the solution"©. :-) When I build log4net I get the following files: * log4net.dll * log4net.pdb * log4net.xml The latter is a parseable output of all the classes, methods, pro

Re: Log4net website issue

On 2017-04-19, Dominik Psenner wrote: > From a higher perspective I would also like to see all logging > subprojects to have one website style. Looking at the website of > log4net and log4j those projects appear to be unrelated, whereas the > log4cxx and log4j websites are more alike. Any ideas ho

Re: Log4net website issue

On 2017-04-18, Dominik Psenner wrote: > We probably should at least add a remark that points readers to the > SDK reference and avoid the double effort of maintaining the > documentation on the website too. Likely, in particular since we've broken it twice during the 2.0.x release series. Looks a

[jira] [Commented] (LOG4J2-1886) Remove logger from configuration using code

[ https://issues.apache.org/jira/browse/LOG4J2-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974284#comment-15974284 ] Izek Greenfield commented on LOG4J2-1886: - I think I find the way doing this: {co

PR#72 build failure.

Hi List, I had a minor update on the documentation for which I sent a pull request. Not sure what happened but, the travis build failed. I see a lot of build failures from the PRs, any reason for that? Here’s my pull request. https://github.com/apache/logging-log4j2/pull/72 thanks, Chandra

[GitHub] logging-log4j2 pull request #72: (doc) LOG4J2-1877: updated DefaultRolloverS...

GitHub user tckb opened a pull request: https://github.com/apache/logging-log4j2/pull/72 (doc) LOG4J2-1877: updated DefaultRolloverStrategy documentation hey, I've updated the site documentation to include the default max value of the defaultrolloverstrategy. You can merge this pu