Fwd: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-12 Thread sebb
Please fix this. -- Forwarded message -- From: Projects Date: 12 April 2018 at 03:00 Subject: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf To: Site Development

JDK 11 Early Access build 8 available

2018-04-12 Thread Rory O'Donnell
Hi Ralph, **JDK 11 EA build 8, *under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/11**. ** * * Newly approved Schedule, status & features o http://openjdk.java.net/projects/jdk/11/ * Release Notes: o http://jdk.java.net/11/release-notes *

Re: [log4j] Curious about WatchManager implementation

2018-04-12 Thread Matt Sicker
I'm not sure if it was ever fixed, but I remember that WatchService works terribly on macOS for some reason (it's really laggy or something). On 12 April 2018 at 11:24, Remko Popma wrote: > I remember Ralph looked at it but concluded it wasn’t fit for purpose. I > forget

Re: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-12 Thread Matt Sicker
Fixed and updated on the site (at least for the latest version of the site; the older doap files were never scanned anyways). On 12 April 2018 at 12:05, Matt Sicker wrote: > Figured it out. Should be a link to https://logging.apache.org/. I'll fix > it shortly. > > On 12 April

Re: [log4j] Curious about WatchManager implementation

2018-04-12 Thread Ralph Goers
As Matt said, I originally tried to use WatchService. I don’t remember the details now but do remember that during development I got frustrated with it and decided it was more trouble than it was worth. Ralph > On Apr 12, 2018, at 10:06 AM, Gary Gregory wrote: > > On

Re: [log4j] Curious about WatchManager implementation

2018-04-12 Thread Gary Gregory
On Thu, Apr 12, 2018 at 10:25 AM, Matt Sicker wrote: > I'm not sure if it was ever fixed, but I remember that WatchService works > terribly on macOS for some reason (it's really laggy or something). > This would be JVM and JRE vendor dependent though. Gary > > On 12 April

Re: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-12 Thread Matt Sicker
Figured it out. Should be a link to https://logging.apache.org/. I'll fix it shortly. On 12 April 2018 at 11:12, Matt Sicker wrote: > The value we have is > > https://logging.apache.org/log4j/2.x/"/> > >

Re: [log4j] Curious about WatchManager implementation

2018-04-12 Thread Ralph Goers
Excerpt from LOG4J2-1031 - "I have been working on the file watching of the scripts today. The more I work with it the less I like Java’s WatchService. Java makes no guarantees about how the service works. On my Mac it uses polling - but I don’t see any way to control the frequency.

Re: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-12 Thread Matt Sicker
The value we have is https://logging.apache.org/log4j/2.x/"/> What link should I be using instead? < https://logging.apache.org/log4j/2.x/team-list.html>? On 12 April 2018 at 04:41, sebb

[log4j] Curious about WatchManager implementation

2018-04-12 Thread Gary Gregory
Hi All: Our WatchManager pools on a thread to watch files. Is there any reason why we are not using Java 7's WatchService? Yes, I know it only watches folders and not files but I consider that a detail ;-) Gary