Re: [Log4j] Lucene 5 Appender

It is fine as long as it is documented that it can and why. Ralph > On Jul 16, 2017, at 11:22 PM, Gary Gregory wrote: > > On Sun, Jul 16, 2017 at 11:20 PM, Ralph Goers > wrote: > >> If there is no split then events could be lost during a reconfigure. >> > > Yes, I know. I am wondering if we

Re: [Log4j] Lucene 5 Appender

I should add that it isn’t very likely though. Ralph > On Jul 16, 2017, at 11:20 PM, Ralph Goers wrote: > > If there is no split then events could be lost during a reconfigure. > > Ralph > >> On Jul 16, 2017, at 11:18 PM, Gary Gregory wrote: >> >> Hi All: >> >> I have a Lucene5 branch base

Re: [Log4j] Lucene 5 Appender

On Sun, Jul 16, 2017 at 11:20 PM, Ralph Goers wrote: > If there is no split then events could be lost during a reconfigure. > Yes, I know. I am wondering if we should allow for this issue in this new module and let users provide patches. Gary > > Ralph > > > On Jul 16, 2017, at 11:18 PM, Gary

Re: [Log4j] Lucene 5 Appender

If there is no split then events could be lost during a reconfigure. Ralph > On Jul 16, 2017, at 11:18 PM, Gary Gregory wrote: > > Hi All: > > I have a Lucene5 branch based on a patch from a user which said user has in > production. > > The only obvious failing I see is that there is no split

[Log4j] Lucene 5 Appender

Hi All: I have a Lucene5 branch based on a patch from a user which said user has in production. The only obvious failing I see is that there is no split between appender and manager. The manager split could be done later. I am wondering if anyone has time to code review the branch. Thank you, G

[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&focusedCommentId=16089353#comment-16089353 ] ASF subversion and git services commented on LOG4J2-1864: - 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&focusedCommentId=16089354#comment-16089354 ] ASF subversion and git services commented on LOG4J2-1864: - Commit

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

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

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

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

[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 Well, the case runs well on my computer. But I notice that the `MAX_STRING_BUILDER_SIZE` is not a constant, instead it may be loaded from the sysstem properties. So I changed my test case, to

[jira] [Commented] (LOG4J2-1949) On failover from JDBC appender, contents of buffer are not written to failover appender

[ https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089306#comment-16089306 ] Gary Gregory commented on LOG4J2-1949: -- I just started looking at this patch by crea

Re: logging-log4j2 git commit: Rename ConfigurationStoppingAware to ConfigurationStopAware since we are piggy backing a stop() method at some point up the call stack.

Yeah, could be. I just started looking at this patch/branch. I am wondering if we can reuse our {{LifeCyle}} and {{LifeCycle2}} interfaces instead of creating new interfaces like {{ConfigurationStoppingAware}}. Something like {{ConfigurationStoppingAware}} seems mighty specific. It is indeed wel

Re: logging-log4j2 git commit: Rename ConfigurationStoppingAware to ConfigurationStopAware since we are piggy backing a stop() method at some point up the call stack.

Maybe ConfigurationLifecycleAware or something? On 16 July 2017 at 22:18, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/LOG4J2-1949 28fb868a0 -> 19a59e680 > > > Rename ConfigurationStoppingAware to ConfigurationStopAware since we are > piggy backing a stop() method at so

Build failed in Jenkins: Log4j 2.x #2905

See Changes: [ggregory] Javadoc. -- [...truncated 1.06 MB...] [INFO] Building jar:

[jira] [Commented] (LOG4J2-1949) On failover from JDBC appender, contents of buffer are not written to failover appender

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

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089227#comment-16089227 ] Matt Sicker commented on LOG4J2-1971: - It's easier to just drop the jars in the deplo

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089201#comment-16089201 ] Ralph Goers commented on LOG4J2-1971: - You are absolutely correct. Adding the file ur

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089200#comment-16089200 ] Gary Gregory commented on LOG4J2-1971: -- I only tried too install and start log4j-api

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089199#comment-16089199 ] Gary Gregory commented on LOG4J2-1971: -- On my setup I got that error when I did not

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

If the version number is an issue and we'd prefer a different module name with a version 1.0, then everything changes quite a bit. If we want to use a smaller version number as the initial release, that's a lot simpler. On 16 July 2017 at 18:34, Matt Sicker wrote: > A bit like Java 9 when you th

Re: More build problems.

I was wondering about that and figured it had something to do with Java 8. Thanks for fixing it! On 16 July 2017 at 17:37, Ralph Goers wrote: > There is an error saying Jenkins doesn’t support Java 7 any for running > Maven and that toolchains has to be used to compile and test using Java 7. > >

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

A bit like Java 9 when you think of it. ;) I'm not sure why they used an artefact naming scheme rather than use classifiers or something more sensible, but then again, I'm not sure if Ivy supports that as it is (it seems as though every JVM build tool other than Maven still uses Ivy). On 16 July

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089171#comment-16089171 ] Ralph Goers edited comment on LOG4J2-1971 at 7/16/17 10:51 PM:

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089171#comment-16089171 ] Ralph Goers edited comment on LOG4J2-1971 at 7/16/17 10:51 PM:

[jira] [Comment Edited] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089171#comment-16089171 ] Ralph Goers edited comment on LOG4J2-1971 at 7/16/17 10:50 PM:

Build failed in Jenkins: Log4j 2.x #2904

See -- [...truncated 1.06 MB...] [INFO] [INFO] --- maven-source-plugin:3.0.1:test-jar-no-fork (attach-sources) @ log4j-web --- [INFO] Building jar:

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089171#comment-16089171 ] Ralph Goers commented on LOG4J2-1971: - Well, it worked for me yesterday. Today I get

Re: More build problems.

There is an error saying Jenkins doesn’t support Java 7 any for running Maven and that toolchains has to be used to compile and test using Java 7. The fix for this is to configure the Jenkins job to use Java 8 by default and to use the Java 7 toolchain when a system property is set. I’ve done th

[jira] [Commented] (LOG4J2-1971) ClassCastException: org.eclipse.osgi.internal.loader.SystemBundleLoader$1 cannot be cast to java.lang.ClassLoader

[ https://issues.apache.org/jira/browse/LOG4J2-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089161#comment-16089161 ] Gary Gregory commented on LOG4J2-1971: -- This is what I get with the latest: {noforma

[jira] [Commented] (LOG4J2-1979) Refactoring of StrSubstitutor

[ https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089159#comment-16089159 ] João Paulo Lemes Machado commented on LOG4J2-1979: -- I totally agree. Dis

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Ah right, since Scale is fond on breaking compatibility. Gary On Jul 16, 2017 14:49, "Ralph Goers" wrote: > Apparently the module name has to have a Scala version number in it. > > Ralph > > > On Jul 16, 2017, at 2:41 PM, Gary Gregory > wrote: > > > > Like log4j-api-scala-wrapper? > > > > Gary

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Apparently the module name has to have a Scala version number in it. Ralph > On Jul 16, 2017, at 2:41 PM, Gary Gregory wrote: > > Like log4j-api-scala-wrapper? > > Gary > > On Jul 16, 2017 14:04, "Ralph Goers" wrote: > >> To address Gary’s issues I think it would be better to use a differen

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Like log4j-api-scala-wrapper? Gary On Jul 16, 2017 14:04, "Ralph Goers" wrote: > To address Gary’s issues I think it would be better to use a different > module name and start from version 1.0. > > Ralph > > > On Jul 16, 2017, at 1:43 PM, Gary Gregory > wrote: > > > > I know... :-( > > > > The

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089126#comment-16089126 ] Gary Gregory commented on LOG4J2-1852: -- Let's not forget that the simplest solution

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

To address Gary’s issues I think it would be better to use a different module name and start from version 1.0. Ralph > On Jul 16, 2017, at 1:43 PM, Gary Gregory wrote: > > I know... :-( > > The checksums are generated either by some Maven plugin or Nexus. > > Gary > > On Sun, Jul 16, 2017 a

Re: [log4j] site pet peeve

Yeah, if you look at the way the site works that is all driven by the site plugin. If you have the time to redo the site, be my guest. I have lots of other things that are higher priority to me. Ralph > On Jul 16, 2017, at 11:53 AM, Matt Sicker wrote: > > I don't think it's simple in the slig

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089115#comment-16089115 ] Gary Gregory commented on LOG4J2-1852: -- Are you able to provide a patch? Gary > Pl

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

I know... :-( The checksums are generated either by some Maven plugin or Nexus. Gary On Sun, Jul 16, 2017 at 1:38 PM, Mikael Ståldal wrote: > The md5sum and sha1sum tools are able to do the comparations themself if > the checksum file contains the filename, which those checksum files > doesn't

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

The md5sum and sha1sum tools are able to do the comparations themself if the checksum file contains the filename, which those checksum files doesn't. Why not? We need to automate this, it's tedious and error-prone to do all this checksum verification manually. On 2017-07-16 22:29, Gary Greg

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

On Sun, Jul 16, 2017 at 1:27 PM, Mikael Ståldal wrote: > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; > 2015-11-10T17:41:47+01:00) > Maven home: /opt/apache-maven-3.3.9 > Java version: 1.8.0_131, vendor: Oracle Corporation > Java home: /opt/jvm/jdk1.8.0_131/jre > Default locale:

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: /opt/apache-maven-3.3.9 Java version: 1.8.0_131, vendor: Oracle Corporation Java home: /opt/jvm/jdk1.8.0_131/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.4.0-8

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

As a PMC, we think we need to better document our "+1"s than "Everything seems fine." For example: Did you check the ASC, MD5 and SHA1 files? _How_ exactly does it "seem" fine? What JDK(s) did you use to build? What did you build? From what? The tag? The zip? And so on. Gary On Sun, Jul 16, 2

Re: [log4j2] sys props driving me nuts

On Sun, Jul 16, 2017 at 12:29 PM, Matt Sicker wrote: > I don't think I'll have time to manage the merge conflicts today, though I > can shoot for tomorrow. > That's great. I just wanted to check that it was still on your near term to-do list. Gary > > On 16 July 2017 at 14:14, Gary Gregory w

Re: [log4j2] sys props driving me nuts

I don't think I'll have time to manage the merge conflicts today, though I can shoot for tomorrow. On 16 July 2017 at 14:14, Gary Gregory wrote: > HI Matt, > > Do you still plan to do this over this weekend? > > Thank you, > Gary > > On Sun, Jul 16, 2017 at 10:02 AM, Matt Sicker wrote: > > > I

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Why is the Maven module name so important? On 2017-07-16 21:11, Gary Gregory wrote: I like my rename suggestion the best which makes the actual version number less confusing (for me) even if it could be somewhat misleading due to version inflation. And I'll leave it at that ;-) Gary On Sun,

Re: [log4j2] sys props driving me nuts

HI Matt, Do you still plan to do this over this weekend? Thank you, Gary On Sun, Jul 16, 2017 at 10:02 AM, Matt Sicker wrote: > I found the issues: > > https://issues.apache.org/jira/browse/LOG4J2-1431 (for the system > properties normalization) > https://issues.apache.org/jira/browse/LOG4J2-1

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

I like my rename suggestion the best which makes the actual version number less confusing (for me) even if it could be somewhat misleading due to version inflation. And I'll leave it at that ;-) Gary On Sun, Jul 16, 2017 at 12:02 PM, Matt Sicker wrote: > I also considered starting with version

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

+1 Everything seems fine. On 2017-07-16 18:41, Matt Sicker wrote: Hello all, sorry for the delay between release candidates. This is a vote to release RC2 of Log4j Scala API 11.0, the first release of the new repository. The main features in this release are Scala 2.12 support and an API for m

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

I also considered starting with version 1.0, but since we've already released a few versions in the 2.x line of this exact groupId/artifactId combo, it wouldn't make sense to start anywhere earlier than 2.8.2 currently. On 16 July 2017 at 13:52, Matt Sicker wrote: > This only requires log4j-api

Re: [log4j] site pet peeve

I don't think it's simple in the slightest to update the current site to be more dynamic using the maven-site-plugin. We may be better off using Gitbook or Asciidoc or something more modern which tend to have more modern themes available. On 16 July 2017 at 13:42, Gary Gregory wrote: > On Sun, J

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

This only requires log4j-api as a dependency, and as we've seen in log4j-core et al, we can require a minimum log4j-api version and simply release the Scala API after log4j-core releases. It'll be too confusing if the version numbers were similar. Perhaps it might make more sense to use version 3.

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Would it be unreasonable to call this Log4jScala? Then you do not have to deal with the whole "for Log4j API" postfix. Alternatively "*Log4j API **wrapper **for Scala 2.10 11.0*" Gary On Sun, Jul 16, 2017 at 11:37 AM, Mikael Ståldal wrote: > This is version 11.0 of the Scala 2.10 wrapper for

Re: [log4j] site pet peeve

On Sun, Jul 16, 2017 at 11:36 AM, Robert Middleton wrote: > On Sun, Jul 16, 2017 at 1:56 PM, Gary Gregory > wrote: > > > Hi All: > > > > A site pet peeve of mine is that when you click on a chevron in the nav > > bar, the whole page is re-drawn. SO LAME! Does anyone know if that is > > something

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

This is version 11.0 of the Scala 2.10 wrapper for Log2j API. "version 11.0" applies to "Scala 2.10 wrapper for Log2j API", not to "Log2j API". The Maven output make this a bit unclear, not sure what we can do about it. On 2017-07-16 20:32, Gary Gregory wrote: On Sun, Jul 16, 2017 at 11:27

Re: [log4j] site pet peeve

On Sun, Jul 16, 2017 at 1:56 PM, Gary Gregory wrote: > Hi All: > > A site pet peeve of mine is that when you click on a chevron in the nav > bar, the whole page is re-drawn. SO LAME! Does anyone know if that is > something a newer version of bootstrap would fix? This can't be a skin > issue, can

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

On Sun, Jul 16, 2017 at 11:27 AM, Gary Gregory wrote: > On Sun, Jul 16, 2017 at 11:17 AM, Gary Gregory > wrote: > >> This is confusing. What are we doing an RC for here? One wrapper? Or all >> of them? Why is this version 11? There is no version 11 of anything. There >> is Scala 2.11 that I see.

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

On Sun, Jul 16, 2017 at 11:28 AM, Matt Sicker wrote: > On 16 July 2017 at 13:27, Gary Gregory wrote: > > > > "Building Scala 2.10 wrapper for Log4j API 11.0" > > > > Where do you see this? > Maven build output. Gary > > > > Uh? > > > > Gary > > > > > > > > > > Gary > > > > > > On Sun, Jul 16,

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

On Sun, Jul 16, 2017 at 11:25 AM, Mikael Ståldal wrote: > We decided to decouple the versioning of this Scala API from the rest of > Logj4, therefore we bumped the version up to 11.0 to make that clear. The > 11 is not related to Scala 2.11. > Still arbitrary silliness AND confusing why not vers

Re: More build problems.

I didn't on that computer yet as I had just installed Java 9 for the first time on it this morning. On 16 July 2017 at 13:10, Ralph Goers wrote: > If you set the default JAVA_HOME how did the java 9 install override it? > > Ralph > > > On Jul 16, 2017, at 9:28 AM, Matt Sicker wrote: > > > > Nor

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

On 16 July 2017 at 13:27, Gary Gregory wrote: > > "Building Scala 2.10 wrapper for Log4j API 11.0" > > Where do you see this? > Uh? > > Gary > > > > > > Gary > > > > On Sun, Jul 16, 2017 at 9:41 AM, Matt Sicker wrote: > > > >> Hello all, sorry for the delay between release candidates. This is a

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

On Sun, Jul 16, 2017 at 11:17 AM, Gary Gregory wrote: > This is confusing. What are we doing an RC for here? One wrapper? Or all > of them? Why is this version 11? There is no version 11 of anything. There > is Scala 2.11 that I see. Is this a typo? > > When I dig a round the repo site from the l

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

I'm not sure what plugins are available for Scala builds yet as I'm still rather new to the Scala ecosystem. I was thinking it might be simpler to find this stuff by switching to SBT for this subproject, though I'll still have to explore a bit to find out. On 16 July 2017 at 13:26, Gary Gregory w

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Never mind about CLIRR blowing up, I was using Java 7, instead of 8. Gary On Sun, Jul 16, 2017 at 11:26 AM, Gary Gregory wrote: > Is there a CLIRR plugin for Scala? 'cause 'mvn clean clirr:check' blows up. > > > Gary > > On Sun, Jul 16, 2017 at 9:41 AM, Matt Sicker wrote: > >> Hello all, sorry

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

This is purely the Log4j Scala API. We're releasing it separately now because it requires Java 8 to build to support Scala 2.12. The version is 11 because it's on its own release train, so we jumped ahead. On 16 July 2017 at 13:17, Gary Gregory wrote: > This is confusing. What are we doing an R

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

We decided to decouple the versioning of this Scala API from the rest of Logj4, therefore we bumped the version up to 11.0 to make that clear. The 11 is not related to Scala 2.11. The important thing here is supporting Scala 2.12 (which requires Java 8). On 2017-07-16 20:17, Gary Gregory wrot

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

Is there a CLIRR plugin for Scala? 'cause 'mvn clean clirr:check' blows up. Gary On Sun, Jul 16, 2017 at 9:41 AM, Matt Sicker wrote: > Hello all, sorry for the delay between release candidates. This is a vote > to release RC2 of Log4j Scala API 11.0, the first release of the new > repository.

Re: [VOTE] Release Log4j Scala API version 11.0 RC2

This is confusing. What are we doing an RC for here? One wrapper? Or all of them? Why is this version 11? There is no version 11 of anything. There is Scala 2.11 that I see. Is this a typo? When I dig a round the repo site from the link, I found a distro zip, which includes ALL the wrappers. OK, g

Re: More build problems.

If you set the default JAVA_HOME how did the java 9 install override it? Ralph > On Jul 16, 2017, at 9:28 AM, Matt Sicker wrote: > > Normally I set my default JAVA_HOME to 1.8 since 1.9 hasn't been compatible > with everything. Otherwise, I'll manually override JAVA_HOME on projects > that requ

[log4j] site pet peeve

Hi All: A site pet peeve of mine is that when you click on a chevron in the nav bar, the whole page is re-drawn. SO LAME! Does anyone know if that is something a newer version of bootstrap would fix? This can't be a skin issue, can it? Gary

Re: [log4j2] sys props driving me nuts

I found the issues: https://issues.apache.org/jira/browse/LOG4J2-1431 (for the system properties normalization) https://issues.apache.org/jira/browse/LOG4J2-1809 (for the supporting API addition to log4j-api) On 14 July 2017 at 15:52, Gary Gregory wrote: > On Fri, Jul 14, 2017 at 1:49 PM, Matt

Re: Build failed in Jenkins: Log4j 2.x #2902

Oh no, the Java 9 support has changed somehow. On 16 July 2017 at 11:57, Apache Jenkins Server wrote: > See redirect?page=changes> > > Changes: > > [matthias.kappeller] Support capped collection for MongoDB Log-Provider > > [matthias.kap

Build failed in Jenkins: Log4j 2.x #2902

See Changes: [matthias.kappeller] Support capped collection for MongoDB Log-Provider [matthias.kappeller] LOG4J2-1864: Introduce builder to MongoDbProvider to preserve backwards [Matt Sicker] [LOG4J2-1864] Update m

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

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1864. - Resolution: Fixed Fix Version/s: 2.9 Merged to master. I've added some basic doc updates f

[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&focusedCommentId=16089019#comment-16089019 ] ASF subversion and git services commented on LOG4J2-1864: - 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&focusedCommentId=16089020#comment-16089020 ] ASF subversion and git services commented on LOG4J2-1864: - 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&focusedCommentId=16089021#comment-16089021 ] ASF GitHub Bot commented on LOG4J2-1864: Github user asfgit closed the pull reque

[GitHub] logging-log4j2 pull request #62: (LOG4J2-1864) Support capped collection for...

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/62 --- 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-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&focusedCommentId=16089018#comment-16089018 ] ASF subversion and git services commented on LOG4J2-1864: - Commit

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

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-1864: --- Assignee: Matt Sicker > Support capped collection for MongoDB Log-Provider > ---

[VOTE] Release Log4j Scala API version 11.0 RC2

Hello all, sorry for the delay between release candidates. This is a vote to release RC2 of Log4j Scala API 11.0, the first release of the new repository. The main features in this release are Scala 2.12 support and an API for manipulating the ThreadContext. Artifacts are available in this staging

Jenkins build is back to normal : Log4jScala #60

See

Re: build.apache.org down

Ah, thanks! My fault that i missed the notification. :-) sorry for the noise. On 16 Jul 2017 6:33 p.m., "Stefan Bodewig" wrote: > On 2017-07-16, Dominik Psenner wrote: > > > I just noticed that since midnight no builds are going through, probably > > caused by a large part of the build slaves th

Build failed in Jenkins: Log4jScala #59

See Changes: [Matt Sicker] [maven-release-plugin] prepare release 11.0-rc2 -- [...truncated 47.38 KB...] [INFO]

Re: More build problems.

Normally I set my default JAVA_HOME to 1.8 since 1.9 hasn't been compatible with everything. Otherwise, I'll manually override JAVA_HOME on projects that require an earlier version. On 16 July 2017 at 11:25, Ralph Goers wrote: > How are you configuring your environment? I set my path and JAVA_HO

Re: [1/2] logging-log4j2 git commit: LOG4J2-1971 - Register Log4j-core as a service. Bypass tests that don't work on MacOS

I mean you can wrap the version into the Version class rather than use a double. It has built in logic for comparing API versions, so for example, if Log4j 2.10.0 becomes a required API version, you won't be comparing 2.100 with 2.60. On 16 July 2017 at 11:21, Ralph Goers wrote: > This is the ef

Re: More build problems.

How are you configuring your environment? I set my path and JAVA_HOME in /etc/profile. The Java installs never mess with that so the only “default” Java I have ever seen is the one I have configured. Ralph > On Jul 16, 2017, at 9:20 AM, Matt Sicker wrote: > > Now that I'm trying this new buil

Re: build.apache.org down

Alright, found something here [1]. Gavin commented on the issue on the 14. July that jenkins is going through a maintenance downtime after two days. So that would be today. [1] https://issues.apache.org/jira/browse/INFRA-14494?focusedCommentId=16087206&page=com.atlassian.jira.plugin.system.issueta

Re: [1/2] logging-log4j2 git commit: LOG4J2-1971 - Register Log4j-core as a service. Bypass tests that don't work on MacOS

This is the effective version of Log4j-API (i.e. the last API version that would impact an implementation). That hasn’t changed since 2.6. Ralph > On Jul 16, 2017, at 8:59 AM, Matt Sicker wrote: > > If this is purely OSGi, you can use their Version class for a better way of > comparing version

Re: More build problems.

Now that I'm trying this new build style out for the first time, I've got some notes: 1. After installing Java 9, it's set to be the default JAVA_HOME if you don't have one set. Maven has some JAXB-related missing module errors currently (could be a plugin, could be Maven itself), so make sure to

Re: build.apache.org down

FYI, the master node is offline but at the same time it is "in sync" and has a latency of "0 ms". 2017-07-16 18:09 GMT+02:00 Dominik Psenner : > Hi, > > I just noticed that since midnight no builds are going through, probably > caused by a large part of the build slaves that are offline. Has anyo

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088985#comment-16088985 ] Matt Sicker commented on LOG4J2-1431: - [~garydgregory] this is the ticket I mentioned

build.apache.org down

Hi, I just noticed that since midnight no builds are going through, probably caused by a large part of the build slaves that are offline. Has anyone of you received a notification for a maintenance downtime? See: https://builds.apache.org/computer/ Cheers -- Dominik Psenner

[jira] [Commented] (LOG4J2-1979) Refactoring of StrSubstitutor

[ https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088983#comment-16088983 ] Matt Sicker commented on LOG4J2-1979: - I think it might be simpler to start refactori

Re: [1/2] logging-log4j2 git commit: LOG4J2-1971 - Register Log4j-core as a service. Bypass tests that don't work on MacOS

If this is purely OSGi, you can use their Version class for a better way of comparing versions. On 15 July 2017 at 11:30, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 8133b6a02 -> 9a08eb08f > > > LOG4J2-1971 - Register Log4j-core as a service. Bypass tests that d

[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&focusedCommentId=16088961#comment-16088961 ] ASF GitHub Bot commented on LOG4J2-1864: Github user jvz commented on the issue:

[GitHub] logging-log4j2 issue #62: (LOG4J2-1864) Support capped collection for MongoD...

Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/62 I'm not too experienced with Mongo either because I prefer not losing data, but no worries, I'll take care of merging this now that I've got some time. --- If your project is set up for it, you c

[jira] [Comment Edited] (LOG4J2-1979) Refactoring of StrSubstitutor

[ https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088940#comment-16088940 ] João Paulo Lemes Machado edited comment on LOG4J2-1979 at 7/16/17 2:29 PM:

[jira] [Commented] (LOG4J2-1979) Refactoring of StrSubstitutor

[ https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088940#comment-16088940 ] João Paulo Lemes Machado commented on LOG4J2-1979: -- I've also found refa

Re: More build problems.

Hello Ralph, noted and thanks, apologies I have no mac to test with. Le sam. 15 juil. 2017 à 05:51, Ralph Goers a écrit : > OK - I have verified that FileAppenderPermissionsTest is flawed on OS X. > It is reading /etc/groups to find a group for the user. If it doesn’t find > a group then it trie

Re: Log4j 2 build hangs

Confirming on El Capitan. On Jul 15, 2017 9:38 AM, "Mikael Ståldal" wrote: > This test works on Java 7, but fails on Java 8 and Java 9: > > [ERROR] Failures: > [ERROR] RollingAppenderDirectWriteWithReconfigureTest.testRollingFil > eAppenderWithReconfigure:68 > Expected: is <2> > but: was <1

  1   2   >