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

[Gary Gregory (JIRA)]

Gary Gregory created LOG4J2-1869:


 Summary: Update Kafka client from 0.10.1.1 to 0.10.2.0
 Key: LOG4J2-1869
 URL: https://issues.apache.org/jira/browse/LOG4J2-1869
 Project: Log4j 2
  Issue Type: Improvement
  Components: Appenders
Affects Versions: 2.8.2
Reporter: Gary Gregory


Update Kafka client from 0.10.1.1 to 0.10.2.0



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

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

[Gary Gregory (JIRA)]

Gary Gregory created LOG4J2-1868:


 Summary: Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0
 Key: LOG4J2-1868
 URL: https://issues.apache.org/jira/browse/LOG4J2-1868
 Project: Log4j 2
  Issue Type: Improvement
Affects Versions: 2.8.2
Reporter: Gary Gregory


Update ZeroMQ's JeroMQ from 0.3.6 to 0.4.0



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

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

[Matt Sicker]

These windows jenkins builds don't seem super stable anyways. Not many
apache projects are using them, so it could be environmental.

On 7 April 2017 at 19:24, Gary Gregory  wrote:

> Note that I ran a full build before this commit (mvn clean install) and it
> worked.
>
> Gary
>
> -- Forwarded message --
> From: Apache Jenkins Server 
> Date: Fri, Apr 7, 2017 at 5:08 PM
> Subject: Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8
> (unlimited security) 64-bit Windows only #51
> To: log4j-dev@logging.apache.org
>
>
> See  =Windows,jdk=JDK%201.8%20(unlimited%20security)%2064-
> bit%20Windows%20only/51/display/redirect?page=changes>
>
> Changes:
>
> [ggregory] Upadate Apache Active MQ from 5.14.1 to 5.14.2 for testing.
>
> --
> [...truncated 383.81 KB...]
> 2017-04-08 00:06:43,683 main DEBUG PatternLayout$Builder(pattern="%m%n",
> PatternSelector=null, Configuration(PropertiesConfigTest), Replace=null,
> charset="null", alwaysWriteExceptions="null", disableAnsi="null",
> noConsoleNoAnsi="null", header="null", footer="null")
> 2017-04-08 00:06:43,684 main DEBUG PluginManager 'Converter' found 41
> plugins
> 2017-04-08 00:06:43,685 main DEBUG Building Plugin[name=appender,
> class=org.apache.logging.log4j.core.appender.ConsoleAppender].
> 2017-04-08 00:06:43,696 main DEBUG ConsoleAppender$Builder(target="null",
> follow="null", direct="null", bufferedIo="null", bufferSize="null",
> immediateFlush="null", ignoreExceptions="null", PatternLayout(%m%n),
> name="STDOUT", Configuration(PropertiesConfigTest), Filter=null)
> 2017-04-08 00:06:43,697 main WARN Unable to instantiate
> org.fusesource.jansi.WindowsAnsiOutputStream
> 2017-04-08 00:06:43,698 main DEBUG Starting OutputStreamManager
> SYSTEM_OUT.false.false
> 2017-04-08 00:06:43,698 main DEBUG Building Plugin[name=layout,
> class=org.apache.logging.log4j.core.layout.PatternLayout].
> 2017-04-08 00:06:43,699 main DEBUG PatternLayout$Builder(pattern="%d %p
> %C{1.} [%t] %m%n", PatternSelector=null, Configuration(PropertiesConfigTest),
> Replace=null, charset="null", alwaysWriteExceptions="null",
> disableAnsi="null", noConsoleNoAnsi="null", header="null", footer="null")
> 2017-04-08 00:06:43,744 main DEBUG Building Plugin[name=appender,
> class=org.apache.logging.log4j.core.appender.FileAppender].
> 2017-04-08 00:06:43,763 main DEBUG 
> FileAppender$Builder(fileName="target/test-properties.log",
> append="null", locking="null", advertise="null", advertiseUri="null",
> createOnDemand="null", bufferedIo="false", bufferSize="null",
> immediateFlush="null", ignoreExceptions="null", PatternLayout(%d %p %C{1.}
> [%t] %m%n), name="File", Configuration(PropertiesConfigTest), Filter=null)
> 2017-04-08 00:06:43,763 main WARN The bufferSize is set to 8192 but
> bufferedIo is false: false
> 2017-04-08 00:06:43,770 main DEBUG Starting FileManager
> target/test-properties.log
> 2017-04-08 00:06:43,770 main DEBUG Building Plugin[name=filter,
> class=org.apache.logging.log4j.core.filter.ThresholdFilter].
> 2017-04-08 00:06:43,773 main DEBUG createFilter(level="ERROR",
> onMatch="null", onMismatch="null")
> 2017-04-08 00:06:43,773 main DEBUG Building Plugin[name=appender,
> class=org.apache.logging.log4j.test.appender.ListAppender].
> 2017-04-08 00:06:43,777 main DEBUG ListAppender$Builder(name="List",
> entryPerNewLine="null", raw="null", Layout=null, ThresholdFilter(ERROR))
> 2017-04-08 00:06:43,778 main DEBUG Building Plugin[name=appenders,
> class=org.apache.logging.log4j.core.config.AppendersPlugin].
> 2017-04-08 00:06:43,778 main DEBUG createAppenders(={STDOUT, File, List})
> 2017-04-08 00:06:43,779 main DEBUG Building Plugin[name=filter,
> class=org.apache.logging.log4j.core.filter.ThresholdFilter].
> 2017-04-08 00:06:43,779 main DEBUG createFilter(level="DEBUG",
> onMatch="null", onMismatch="null")
> 2017-04-08 00:06:43,781 main DEBUG Configuration
> org.apache.logging.log4j.core.config.properties.PropertiesCo
> nfiguration@31ef45e3 initialized
> 2017-04-08 00:06:43,782 main DEBUG Starting configuration
> org.apache.logging.log4j.core.config.properties.PropertiesCo
> nfiguration@31ef45e3
> 2017-04-08 00:06:43,783 main DEBUG Log4j2 ConfigurationScheduler starting
> 1 threads
> 2017-04-08 00:06:43,785 main DEBUG Started configuration
> org.apache.logging.log4j.core.config.properties.PropertiesCo
> nfiguration@31ef45e3 OK.
> 2017-04-08 00:06:43,786 main DEBUG Shutting down OutputStreamManager
> SYSTEM_OUT.false.false-1
> 2017-04-08 00:06:43,787 main DEBUG Shut down OutputStreamManager
> SYSTEM_OUT.false.false-1, all resources released: true
> 2017-04-08 00:06:43,787 main DEBUG Appender DefaultConsole-1 stopped with
> status true
> 2017-04-08 00:06:43,788 main DEBUG Stopped org.apache.logging.log4j.core.
> config.DefaultConfiguration@7921b0a2 OK
> 2017-04-08 00:06:43,981 main DEBUG Registering MBean
> 

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

[Apache Jenkins Server]

See 


Changes:

[garydgregory] Upadate Apache Active MQ from 5.14.3 to 5.14.4 for testing.

--
[...truncated 392.38 KB...]
2017-04-08 01:11:53,749 main DEBUG Building Plugin[name=loggers, 
class=org.apache.logging.log4j.core.config.LoggersPlugin].
2017-04-08 01:11:53,750 main DEBUG 
createLoggers(={org.apache.logging.log4j.test2, org.apache.logging.log4j.test1, 
root})
2017-04-08 01:11:53,752 main DEBUG Building Plugin[name=layout, 
class=org.apache.logging.log4j.core.layout.PatternLayout].
2017-04-08 01:11:53,755 main DEBUG PatternLayout$Builder(pattern="%d %p %C{1.} 
[%t] %m%n", PatternSelector=null, Configuration(PropertiesConfigTest), 
Replace=null, charset="null", alwaysWriteExceptions="null", disableAnsi="null", 
noConsoleNoAnsi="null", header="null", footer="null")
2017-04-08 01:11:53,756 main DEBUG PluginManager 'Converter' found 41 plugins
2017-04-08 01:11:53,788 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.FileAppender].
2017-04-08 01:11:53,798 main DEBUG 
FileAppender$Builder(fileName="target/test-properties.log", append="null", 
locking="null", advertise="null", advertiseUri="null", createOnDemand="null", 
bufferedIo="false", bufferSize="null", immediateFlush="null", 
ignoreExceptions="null", PatternLayout(%d %p %C{1.} [%t] %m%n), name="File", 
Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 01:11:53,798 main WARN The bufferSize is set to 8192 but bufferedIo 
is false: false
2017-04-08 01:11:53,802 main DEBUG Starting FileManager 
target/test-properties.log
2017-04-08 01:11:53,802 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 01:11:53,805 main DEBUG createFilter(level="ERROR", onMatch="null", 
onMismatch="null")
2017-04-08 01:11:53,805 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.test.appender.ListAppender].
2017-04-08 01:11:53,807 main DEBUG ListAppender$Builder(name="List", 
entryPerNewLine="null", raw="null", Layout=null, ThresholdFilter(ERROR))
2017-04-08 01:11:53,807 main DEBUG Building Plugin[name=layout, 
class=org.apache.logging.log4j.core.layout.PatternLayout].
2017-04-08 01:11:53,809 main DEBUG PatternLayout$Builder(pattern="%m%n", 
PatternSelector=null, Configuration(PropertiesConfigTest), Replace=null, 
charset="null", alwaysWriteExceptions="null", disableAnsi="null", 
noConsoleNoAnsi="null", header="null", footer="null")
2017-04-08 01:11:53,809 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.ConsoleAppender].
2017-04-08 01:11:53,814 main DEBUG ConsoleAppender$Builder(target="null", 
follow="null", direct="null", bufferedIo="null", bufferSize="null", 
immediateFlush="null", ignoreExceptions="null", PatternLayout(%m%n), 
name="STDOUT", Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 01:11:53,814 main WARN Unable to instantiate 
org.fusesource.jansi.WindowsAnsiOutputStream
2017-04-08 01:11:53,814 main DEBUG Starting OutputStreamManager 
SYSTEM_OUT.false.false
2017-04-08 01:11:53,815 main DEBUG Building Plugin[name=appenders, 
class=org.apache.logging.log4j.core.config.AppendersPlugin].
2017-04-08 01:11:53,815 main DEBUG createAppenders(={File, List, STDOUT})
2017-04-08 01:11:53,816 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 01:11:53,817 main DEBUG createFilter(level="DEBUG", onMatch="null", 
onMismatch="null")
2017-04-08 01:11:53,817 main DEBUG Configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@5fae6db3
 initialized
2017-04-08 01:11:53,817 main DEBUG Starting configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@5fae6db3
2017-04-08 01:11:53,820 main DEBUG Log4j2 ConfigurationScheduler starting 1 
threads
2017-04-08 01:11:53,821 main DEBUG Started configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@5fae6db3
 OK.
2017-04-08 01:11:53,822 main DEBUG Shutting down OutputStreamManager 
SYSTEM_OUT.false.false-1
2017-04-08 01:11:53,822 main DEBUG Shut down OutputStreamManager 
SYSTEM_OUT.false.false-1, all resources released: true
2017-04-08 01:11:53,823 main DEBUG Appender DefaultConsole-1 stopped with 
status true
2017-04-08 01:11:53,823 main DEBUG Stopped 
org.apache.logging.log4j.core.config.DefaultConfiguration@4f8d0299 OK
2017-04-08 01:11:53,927 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest
2017-04-08 01:11:53,933 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=StatusLogger
2017-04-08 01:11:53,936 main DEBUG Registering MBean 

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

[Apache Jenkins Server]

See 



-
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

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

[Apache Jenkins Server]

See 


Changes:

[garydgregory] Upadate Apache Active MQ from 5.14.2 to 5.14.3 for testing.

--
[...truncated 392.60 KB...]
2017-04-08 00:41:31,720 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.FileAppender].
2017-04-08 00:41:31,728 main DEBUG 
FileAppender$Builder(fileName="target/test-properties.log", append="null", 
locking="null", advertise="null", advertiseUri="null", createOnDemand="null", 
bufferedIo="false", bufferSize="null", immediateFlush="null", 
ignoreExceptions="null", PatternLayout(%d %p %C{1.} [%t] %m%n), name="File", 
Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 00:41:31,729 main WARN The bufferSize is set to 8192 but bufferedIo 
is false: false
2017-04-08 00:41:31,735 main DEBUG Starting FileManager 
target/test-properties.log
2017-04-08 00:41:31,736 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 00:41:31,737 main DEBUG createFilter(level="ERROR", onMatch="null", 
onMismatch="null")
2017-04-08 00:41:31,738 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.test.appender.ListAppender].
2017-04-08 00:41:31,740 main DEBUG ListAppender$Builder(name="List", 
entryPerNewLine="null", raw="null", Layout=null, ThresholdFilter(ERROR))
2017-04-08 00:41:31,741 main DEBUG Building Plugin[name=layout, 
class=org.apache.logging.log4j.core.layout.PatternLayout].
2017-04-08 00:41:31,743 main DEBUG PatternLayout$Builder(pattern="%m%n", 
PatternSelector=null, Configuration(PropertiesConfigTest), Replace=null, 
charset="null", alwaysWriteExceptions="null", disableAnsi="null", 
noConsoleNoAnsi="null", header="null", footer="null")
2017-04-08 00:41:31,743 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.ConsoleAppender].
2017-04-08 00:41:31,746 main DEBUG ConsoleAppender$Builder(target="null", 
follow="null", direct="null", bufferedIo="null", bufferSize="null", 
immediateFlush="null", ignoreExceptions="null", PatternLayout(%m%n), 
name="STDOUT", Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 00:41:31,747 main WARN Unable to instantiate 
org.fusesource.jansi.WindowsAnsiOutputStream
2017-04-08 00:41:31,747 main DEBUG Starting OutputStreamManager 
SYSTEM_OUT.false.false
2017-04-08 00:41:31,748 main DEBUG Building Plugin[name=appenders, 
class=org.apache.logging.log4j.core.config.AppendersPlugin].
2017-04-08 00:41:31,748 main DEBUG createAppenders(={File, List, STDOUT})
2017-04-08 00:41:31,749 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 00:41:31,750 main DEBUG createFilter(level="DEBUG", onMatch="null", 
onMismatch="null")
2017-04-08 00:41:31,751 main DEBUG Configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@94eefbf 
initialized
2017-04-08 00:41:31,751 main DEBUG Starting configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@94eefbf
2017-04-08 00:41:31,753 main DEBUG Log4j2 ConfigurationScheduler starting 1 
threads
2017-04-08 00:41:31,754 main DEBUG Started configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@94eefbf 
OK.
2017-04-08 00:41:31,755 main DEBUG Shutting down OutputStreamManager 
SYSTEM_OUT.false.false-1
2017-04-08 00:41:31,755 main DEBUG Shut down OutputStreamManager 
SYSTEM_OUT.false.false-1, all resources released: true
2017-04-08 00:41:31,756 main DEBUG Appender DefaultConsole-1 stopped with 
status true
2017-04-08 00:41:31,756 main DEBUG Stopped 
org.apache.logging.log4j.core.config.DefaultConfiguration@52052438 OK
2017-04-08 00:41:31,859 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest
2017-04-08 00:41:31,863 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=StatusLogger
2017-04-08 00:41:31,866 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=ContextSelector
2017-04-08 00:41:31,869 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=org.apache.logging.log4j.test2
2017-04-08 00:41:31,870 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=
2017-04-08 00:41:31,870 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=org.apache.logging.log4j.test1
2017-04-08 00:41:31,873 main DEBUG Registering MBean 

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

[Gary Gregory]

Note that I ran a full build before this commit (mvn clean install) and it
worked.

Gary

-- Forwarded message --
From: Apache Jenkins Server 
Date: Fri, Apr 7, 2017 at 5:08 PM
Subject: Build failed in Jenkins: Log4jWindows » Windows,JDK 1.8 (unlimited
security) 64-bit Windows only #51
To: log4j-dev@logging.apache.org


See 

Changes:

[ggregory] Upadate Apache Active MQ from 5.14.1 to 5.14.2 for testing.

--
[...truncated 383.81 KB...]
2017-04-08 00:06:43,683 main DEBUG PatternLayout$Builder(pattern="%m%n",
PatternSelector=null, Configuration(PropertiesConfigTest), Replace=null,
charset="null", alwaysWriteExceptions="null", disableAnsi="null",
noConsoleNoAnsi="null", header="null", footer="null")
2017-04-08 00:06:43,684 main DEBUG PluginManager 'Converter' found 41
plugins
2017-04-08 00:06:43,685 main DEBUG Building Plugin[name=appender,
class=org.apache.logging.log4j.core.appender.ConsoleAppender].
2017-04-08 00:06:43,696 main DEBUG ConsoleAppender$Builder(target="null",
follow="null", direct="null", bufferedIo="null", bufferSize="null",
immediateFlush="null", ignoreExceptions="null", PatternLayout(%m%n),
name="STDOUT", Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 00:06:43,697 main WARN Unable to instantiate
org.fusesource.jansi.WindowsAnsiOutputStream
2017-04-08 00:06:43,698 main DEBUG Starting OutputStreamManager
SYSTEM_OUT.false.false
2017-04-08 00:06:43,698 main DEBUG Building Plugin[name=layout,
class=org.apache.logging.log4j.core.layout.PatternLayout].
2017-04-08 00:06:43,699 main DEBUG PatternLayout$Builder(pattern="%d %p
%C{1.} [%t] %m%n", PatternSelector=null, Configuration(PropertiesConfigTest),
Replace=null, charset="null", alwaysWriteExceptions="null",
disableAnsi="null", noConsoleNoAnsi="null", header="null", footer="null")
2017-04-08 00:06:43,744 main DEBUG Building Plugin[name=appender,
class=org.apache.logging.log4j.core.appender.FileAppender].
2017-04-08 00:06:43,763 main DEBUG
FileAppender$Builder(fileName="target/test-properties.log",
append="null", locking="null", advertise="null", advertiseUri="null",
createOnDemand="null", bufferedIo="false", bufferSize="null",
immediateFlush="null", ignoreExceptions="null", PatternLayout(%d %p %C{1.}
[%t] %m%n), name="File", Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 00:06:43,763 main WARN The bufferSize is set to 8192 but
bufferedIo is false: false
2017-04-08 00:06:43,770 main DEBUG Starting FileManager
target/test-properties.log
2017-04-08 00:06:43,770 main DEBUG Building Plugin[name=filter,
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 00:06:43,773 main DEBUG createFilter(level="ERROR",
onMatch="null", onMismatch="null")
2017-04-08 00:06:43,773 main DEBUG Building Plugin[name=appender,
class=org.apache.logging.log4j.test.appender.ListAppender].
2017-04-08 00:06:43,777 main DEBUG ListAppender$Builder(name="List",
entryPerNewLine="null", raw="null", Layout=null, ThresholdFilter(ERROR))
2017-04-08 00:06:43,778 main DEBUG Building Plugin[name=appenders,
class=org.apache.logging.log4j.core.config.AppendersPlugin].
2017-04-08 00:06:43,778 main DEBUG createAppenders(={STDOUT, File, List})
2017-04-08 00:06:43,779 main DEBUG Building Plugin[name=filter,
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 00:06:43,779 main DEBUG createFilter(level="DEBUG",
onMatch="null", onMismatch="null")
2017-04-08 00:06:43,781 main DEBUG Configuration
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
initialized
2017-04-08 00:06:43,782 main DEBUG Starting configuration
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@
31ef45e3
2017-04-08 00:06:43,783 main DEBUG Log4j2 ConfigurationScheduler starting 1
threads
2017-04-08 00:06:43,785 main DEBUG Started configuration
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
OK.
2017-04-08 00:06:43,786 main DEBUG Shutting down OutputStreamManager
SYSTEM_OUT.false.false-1
2017-04-08 00:06:43,787 main DEBUG Shut down OutputStreamManager
SYSTEM_OUT.false.false-1, all resources released: true
2017-04-08 00:06:43,787 main DEBUG Appender DefaultConsole-1 stopped with
status true
2017-04-08 00:06:43,788 main DEBUG Stopped org.apache.logging.log4j.core.
config.DefaultConfiguration@7921b0a2 OK
2017-04-08 00:06:43,981 main DEBUG Registering MBean
org.apache.logging.log4j2:type=org.apache.logging.log4j.
core.PropertiesFileConfigTest
2017-04-08 00:06:43,990 main DEBUG Registering MBean
org.apache.logging.log4j2:type=org.apache.logging.log4j.
core.PropertiesFileConfigTest,component=StatusLogger
2017-04-08 00:06:43,993 main DEBUG Registering MBean
org.apache.logging.log4j2:type=org.apache.logging.log4j.

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

[Apache Jenkins Server]

See 


Changes:

[ggregory] Upadate Apache Active MQ from 5.14.1 to 5.14.2 for testing.

--
[...truncated 576.11 KB...]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.script) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.sql) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.tools) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.xml.bind) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.xml.parsers) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.xml.stream) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.xml.transform) -> [org.apache.felix.framework [0](R 
0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.xml.transform.stream) -> [org.apache.felix.framework 
[0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=javax.xml.validation) -> [org.apache.felix.framework [0](R 
0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.apache.logging.log4j)(version>=2.8.0)(!(version>=3.0.0)))
 -> [org.apache.logging.log4j.api [1](R 1.0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.apache.logging.log4j.message)(version>=2.8.0)(!(version>=3.0.0)))
 -> [org.apache.logging.log4j.api [1](R 1.0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.apache.logging.log4j.spi)(version>=2.8.0)(!(version>=3.0.0)))
 -> [org.apache.logging.log4j.api [1](R 1.0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.apache.logging.log4j.status)(version>=2.8.0)(!(version>=3.0.0)))
 -> [org.apache.logging.log4j.api [1](R 1.0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.apache.logging.log4j.util)(version>=2.8.0)(!(version>=3.0.0)))
 -> [org.apache.logging.log4j.api [1](R 1.0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0))) 
-> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.framework.wiring)(version>=1.0.0)(!(version>=2.0.0)))
 -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=org.w3c.dom) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.wiring.package; 
(osgi.wiring.package=org.xml.sax) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.core [2](R 2.0)] osgi.ee; 
(&(osgi.ee=JavaSE)(version=1.7)) -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.api [1](R 1.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.framework)(version>=1.6.0)(!(version>=2.0.0))) 
-> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.api [1](R 1.0)] osgi.wiring.package; 
(&(osgi.wiring.package=org.osgi.framework.wiring)(version>=1.0.0)(!(version>=2.0.0)))
 -> [org.apache.felix.framework [0](R 0)]
DEBUG: WIRE: [org.apache.logging.log4j.api [1](R 1.0)] osgi.wiring.package; 
(osgi.wiring.package=org.apache.logging.log4j.core.osgi) -> 
[org.apache.logging.log4j.core [2](R 2.0)]
DEBUG: WIRE: [org.apache.logging.log4j.api [1](R 1.0)] osgi.wiring.package; 
(osgi.wiring.package=org.apache.logging.log4j.core.util) -> 
[org.apache.logging.log4j.core [2](R 2.0)]
DEBUG: WIRE: [org.apache.logging.log4j.api [1](R 1.0)] osgi.ee; 
(&(osgi.ee=JavaSE)(version=1.7)) -> [org.apache.felix.framework [0](R 0)]
DEBUG: Bundle org.apache.logging.log4j.core [2] 
log4j2-testorg.apache.logging.log4j.core.properties not found by 
org.apache.logging.log4j.core [2]
DEBUG: Bundle org.apache.logging.log4j.core [2] 
log4j2-testorg.apache.logging.log4j.core.yml not found by 
org.apache.logging.log4j.core [2]
DEBUG: Bundle org.apache.logging.log4j.core [2] 
log4j2-testorg.apache.logging.log4j.core.yaml not found by 

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

[Apache Jenkins Server]

See 


Changes:

[ggregory] Upadate Apache Active MQ from 5.14.1 to 5.14.2 for testing.

--
[...truncated 383.81 KB...]
2017-04-08 00:06:43,683 main DEBUG PatternLayout$Builder(pattern="%m%n", 
PatternSelector=null, Configuration(PropertiesConfigTest), Replace=null, 
charset="null", alwaysWriteExceptions="null", disableAnsi="null", 
noConsoleNoAnsi="null", header="null", footer="null")
2017-04-08 00:06:43,684 main DEBUG PluginManager 'Converter' found 41 plugins
2017-04-08 00:06:43,685 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.ConsoleAppender].
2017-04-08 00:06:43,696 main DEBUG ConsoleAppender$Builder(target="null", 
follow="null", direct="null", bufferedIo="null", bufferSize="null", 
immediateFlush="null", ignoreExceptions="null", PatternLayout(%m%n), 
name="STDOUT", Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 00:06:43,697 main WARN Unable to instantiate 
org.fusesource.jansi.WindowsAnsiOutputStream
2017-04-08 00:06:43,698 main DEBUG Starting OutputStreamManager 
SYSTEM_OUT.false.false
2017-04-08 00:06:43,698 main DEBUG Building Plugin[name=layout, 
class=org.apache.logging.log4j.core.layout.PatternLayout].
2017-04-08 00:06:43,699 main DEBUG PatternLayout$Builder(pattern="%d %p %C{1.} 
[%t] %m%n", PatternSelector=null, Configuration(PropertiesConfigTest), 
Replace=null, charset="null", alwaysWriteExceptions="null", disableAnsi="null", 
noConsoleNoAnsi="null", header="null", footer="null")
2017-04-08 00:06:43,744 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.core.appender.FileAppender].
2017-04-08 00:06:43,763 main DEBUG 
FileAppender$Builder(fileName="target/test-properties.log", append="null", 
locking="null", advertise="null", advertiseUri="null", createOnDemand="null", 
bufferedIo="false", bufferSize="null", immediateFlush="null", 
ignoreExceptions="null", PatternLayout(%d %p %C{1.} [%t] %m%n), name="File", 
Configuration(PropertiesConfigTest), Filter=null)
2017-04-08 00:06:43,763 main WARN The bufferSize is set to 8192 but bufferedIo 
is false: false
2017-04-08 00:06:43,770 main DEBUG Starting FileManager 
target/test-properties.log
2017-04-08 00:06:43,770 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 00:06:43,773 main DEBUG createFilter(level="ERROR", onMatch="null", 
onMismatch="null")
2017-04-08 00:06:43,773 main DEBUG Building Plugin[name=appender, 
class=org.apache.logging.log4j.test.appender.ListAppender].
2017-04-08 00:06:43,777 main DEBUG ListAppender$Builder(name="List", 
entryPerNewLine="null", raw="null", Layout=null, ThresholdFilter(ERROR))
2017-04-08 00:06:43,778 main DEBUG Building Plugin[name=appenders, 
class=org.apache.logging.log4j.core.config.AppendersPlugin].
2017-04-08 00:06:43,778 main DEBUG createAppenders(={STDOUT, File, List})
2017-04-08 00:06:43,779 main DEBUG Building Plugin[name=filter, 
class=org.apache.logging.log4j.core.filter.ThresholdFilter].
2017-04-08 00:06:43,779 main DEBUG createFilter(level="DEBUG", onMatch="null", 
onMismatch="null")
2017-04-08 00:06:43,781 main DEBUG Configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
 initialized
2017-04-08 00:06:43,782 main DEBUG Starting configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
2017-04-08 00:06:43,783 main DEBUG Log4j2 ConfigurationScheduler starting 1 
threads
2017-04-08 00:06:43,785 main DEBUG Started configuration 
org.apache.logging.log4j.core.config.properties.PropertiesConfiguration@31ef45e3
 OK.
2017-04-08 00:06:43,786 main DEBUG Shutting down OutputStreamManager 
SYSTEM_OUT.false.false-1
2017-04-08 00:06:43,787 main DEBUG Shut down OutputStreamManager 
SYSTEM_OUT.false.false-1, all resources released: true
2017-04-08 00:06:43,787 main DEBUG Appender DefaultConsole-1 stopped with 
status true
2017-04-08 00:06:43,788 main DEBUG Stopped 
org.apache.logging.log4j.core.config.DefaultConfiguration@7921b0a2 OK
2017-04-08 00:06:43,981 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest
2017-04-08 00:06:43,990 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=StatusLogger
2017-04-08 00:06:43,993 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=ContextSelector
2017-04-08 00:06:43,997 main DEBUG Registering MBean 
org.apache.logging.log4j2:type=org.apache.logging.log4j.core.PropertiesFileConfigTest,component=Loggers,name=org.apache.logging.log4j.test1
2017-04-08 00:06:44,002 main DEBUG Registering MBean 

Re: Weird compilation error

[Gary Gregory]

Could be I'm going to run the build with each ActiveMQ release since what
we have and see what happens. I'll nuke the latest one I have just in case
it's junked.

Gary

On Fri, Apr 7, 2017 at 1:49 PM, Matt Sicker  wrote:

> Corrupted downloads perhaps? That's very odd!
>
> On 7 April 2017 at 15:48, Gary Gregory  wrote:
>
>> Hm,
>>
>> I had changed active mq testing from 5.14.1 to 5.14.4 and that yields:
>>
>> [ERROR] error: error reading C:\Users\ggregory\.m2\reposito
>> ry\org\apache\activemq\activemq-broker\5.14.4\activemq-broker-5.14.4.jar;
>> invalid LOC header (bad signature)
>> [ERROR] error: error reading C:\Users\ggregory\.m2\reposito
>> ry\org\apache\activemq\activemq-client\5.14.4\activemq-client-5.14.4.jar;
>> invalid LOC header (bad signature)
>>
>> and later the problems I initially showed.
>>
>> Odd!
>>
>> Gary
>>
>>
>> On Fri, Apr 7, 2017 at 1:41 PM, Gary Gregory 
>> wrote:
>>
>>> I added to log4j-1.2-api:
>>>
>>> 
>>>   org.apache.logging.log4j
>>>   log4j-core
>>>   test
>>>   test
>>> 
>>>
>>> but that blows up Maven 3.3.9:
>>>
>>> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
>>> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
>>> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
>>> declaration of version (?) @ 
>>> org.apache.logging.log4j:log4j-core-its:[unknown-version],
>>> C:\vcs\git\apache\logging\logging-log4j2\log4j-core-its\pom.xml, line
>>> 50, column 17
>>> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
>>> must be unique: org.apache.logging.log4j:log4j-api:test-jar ->
>>> duplicate declaration of version (?) @ 
>>> org.apache.logging.log4j:log4j-core-its:[unknown-version],
>>> C:\vcs\git\apache\logging\logging-log4j2\log4j-core-its\pom.xml, line
>>> 114, column 17
>>> [ERROR] 'dependencies.dependency.version' for
>>> org.apache.logging.log4j:log4j-core:test is missing. @
>>> org.apache.logging.log4j:log4j-1.2-api:[unknown-version],
>>> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\pom.xml, line
>>> 47, column 17
>>> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
>>> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
>>> declaration of version (?) @ 
>>> org.apache.logging.log4j:log4j-slf4j-impl:[unknown-version],
>>> C:\vcs\git\apache\logging\logging-log4j2\log4j-slf4j-impl\pom.xml, line
>>> 70, column 17
>>> [WARNING] 'parent.relativePath' of POM 
>>> org.apache.logging.log4j:log4j-bom:2.8.3-SNAPSHOT
>>> (C:\vcs\git\apache\logging\logging-log4j2\log4j-bom\pom.xml) points at
>>> org.apache.logging.log4j:log4j instead of org.apache.logging:logging-parent,
>>> please verify your project structure @ line 19, column 11
>>>  @
>>>
>>>
>>> Gary
>>>
>>> On Fri, Apr 7, 2017 at 1:34 PM, Gary Gregory 
>>> wrote:
>>>
 This is with Maven 3.3.9 though.

 Gary

 On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:

> Does it have a dependency on log4j-core:test? It should. Could be a
> bug in your beta version of Maven ;)
>
> On 7 April 2017 at 14:46, Gary Gregory  wrote:
>
>> Hi All:
>>
>> I'm seeing this in master:
>>
>> [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @
>> log4j-1.2-api ---
>> [INFO]
>> [INFO] --- maven-resources-plugin:3.0.1:testResources
>> (default-testResources) @ log4j-1.2-api ---
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] Copying 71 resources
>> [INFO] Copying 3 resources
>> [INFO] Copying 3 resources
>> [INFO]
>> [INFO] --- maven-compiler-plugin:3.6.0:testCompile
>> (default-testCompile) @ log4j-1.2-api ---
>> [INFO] Changes detected - recompiling the module!
>> [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
>> ing-log4j2\log4j-1.2-api\target\test-classes
>> [INFO] -
>> [WARN] COMPILATION WARNING :
>> [INFO] -
>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>> est\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
>> [deprecation] setContextMap(Map) in Builder has been
>> deprecated
>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>> est\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
>> [deprecation] setContextMap(Map) in Builder has been
>> deprecated
>> [INFO] 2 warnings
>> [INFO] -
>> [INFO] -
>> [ERROR] COMPILATION ERROR :
>> [INFO] 

Re: Weird compilation error

[Matt Sicker]

Corrupted downloads perhaps? That's very odd!

On 7 April 2017 at 15:48, Gary Gregory  wrote:

> Hm,
>
> I had changed active mq testing from 5.14.1 to 5.14.4 and that yields:
>
> [ERROR] error: error reading C:\Users\ggregory\.m2\repository\org\apache\
> activemq\activemq-broker\5.14.4\activemq-broker-5.14.4.jar; invalid LOC
> header (bad signature)
> [ERROR] error: error reading C:\Users\ggregory\.m2\repository\org\apache\
> activemq\activemq-client\5.14.4\activemq-client-5.14.4.jar; invalid LOC
> header (bad signature)
>
> and later the problems I initially showed.
>
> Odd!
>
> Gary
>
>
> On Fri, Apr 7, 2017 at 1:41 PM, Gary Gregory 
> wrote:
>
>> I added to log4j-1.2-api:
>>
>> 
>>   org.apache.logging.log4j
>>   log4j-core
>>   test
>>   test
>> 
>>
>> but that blows up Maven 3.3.9:
>>
>> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
>> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
>> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
>> declaration of version (?) @ 
>> org.apache.logging.log4j:log4j-core-its:[unknown-version],
>> C:\vcs\git\apache\logging\logging-log4j2\log4j-core-its\pom.xml, line
>> 50, column 17
>> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
>> must be unique: org.apache.logging.log4j:log4j-api:test-jar -> duplicate
>> declaration of version (?) @ 
>> org.apache.logging.log4j:log4j-core-its:[unknown-version],
>> C:\vcs\git\apache\logging\logging-log4j2\log4j-core-its\pom.xml, line
>> 114, column 17
>> [ERROR] 'dependencies.dependency.version' for
>> org.apache.logging.log4j:log4j-core:test is missing. @
>> org.apache.logging.log4j:log4j-1.2-api:[unknown-version],
>> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\pom.xml, line 47,
>> column 17
>> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
>> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
>> declaration of version (?) @ 
>> org.apache.logging.log4j:log4j-slf4j-impl:[unknown-version],
>> C:\vcs\git\apache\logging\logging-log4j2\log4j-slf4j-impl\pom.xml, line
>> 70, column 17
>> [WARNING] 'parent.relativePath' of POM 
>> org.apache.logging.log4j:log4j-bom:2.8.3-SNAPSHOT
>> (C:\vcs\git\apache\logging\logging-log4j2\log4j-bom\pom.xml) points at
>> org.apache.logging.log4j:log4j instead of org.apache.logging:logging-parent,
>> please verify your project structure @ line 19, column 11
>>  @
>>
>>
>> Gary
>>
>> On Fri, Apr 7, 2017 at 1:34 PM, Gary Gregory 
>> wrote:
>>
>>> This is with Maven 3.3.9 though.
>>>
>>> Gary
>>>
>>> On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:
>>>
 Does it have a dependency on log4j-core:test? It should. Could be a bug
 in your beta version of Maven ;)

 On 7 April 2017 at 14:46, Gary Gregory  wrote:

> Hi All:
>
> I'm seeing this in master:
>
> [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @
> log4j-1.2-api ---
> [INFO]
> [INFO] --- maven-resources-plugin:3.0.1:testResources
> (default-testResources) @ log4j-1.2-api ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 71 resources
> [INFO] Copying 3 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:testCompile
> (default-testCompile) @ log4j-1.2-api ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
> ing-log4j2\log4j-1.2-api\target\test-classes
> [INFO] -
> [WARN] COMPILATION WARNING :
> [INFO] -
> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
> est\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
> [deprecation] setContextMap(Map) in Builder has been
> deprecated
> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
> est\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
> [deprecation] setContextMap(Map) in Builder has been
> deprecated
> [INFO] 2 warnings
> [INFO] -
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR] warning: No processor claimed any of these annotations:
> org.junit.AfterClass,org.junit.Before,org.junit.runners.Para
> meterized.Parameters,org.junit.Rule,org.junit.ClassRule,org.
> junit.After,org.junit.runner.RunWith,org.junit.BeforeClass,o
> rg.junit.Test
> 

Re: Weird compilation error

[Gary Gregory]

Hm,

I had changed active mq testing from 5.14.1 to 5.14.4 and that yields:

[ERROR] error: error reading
C:\Users\ggregory\.m2\repository\org\apache\activemq\activemq-broker\5.14.4\activemq-broker-5.14.4.jar;
invalid LOC header (bad signature)
[ERROR] error: error reading
C:\Users\ggregory\.m2\repository\org\apache\activemq\activemq-client\5.14.4\activemq-client-5.14.4.jar;
invalid LOC header (bad signature)

and later the problems I initially showed.

Odd!

Gary


On Fri, Apr 7, 2017 at 1:41 PM, Gary Gregory  wrote:

> I added to log4j-1.2-api:
>
> 
>   org.apache.logging.log4j
>   log4j-core
>   test
>   test
> 
>
> but that blows up Maven 3.3.9:
>
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
> declaration of version (?) @ org.apache.logging.log4j:
> log4j-core-its:[unknown-version], C:\vcs\git\apache\logging\
> logging-log4j2\log4j-core-its\pom.xml, line 50, column 17
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.apache.logging.log4j:log4j-api:test-jar -> duplicate
> declaration of version (?) @ org.apache.logging.log4j:
> log4j-core-its:[unknown-version], C:\vcs\git\apache\logging\
> logging-log4j2\log4j-core-its\pom.xml, line 114, column 17
> [ERROR] 'dependencies.dependency.version' for 
> org.apache.logging.log4j:log4j-core:test
> is missing. @ org.apache.logging.log4j:log4j-1.2-api:[unknown-version],
> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\pom.xml, line 47,
> column 17
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
> declaration of version (?) @ org.apache.logging.log4j:
> log4j-slf4j-impl:[unknown-version], C:\vcs\git\apache\logging\
> logging-log4j2\log4j-slf4j-impl\pom.xml, line 70, column 17
> [WARNING] 'parent.relativePath' of POM 
> org.apache.logging.log4j:log4j-bom:2.8.3-SNAPSHOT
> (C:\vcs\git\apache\logging\logging-log4j2\log4j-bom\pom.xml) points at
> org.apache.logging.log4j:log4j instead of org.apache.logging:logging-parent,
> please verify your project structure @ line 19, column 11
>  @
>
>
> Gary
>
> On Fri, Apr 7, 2017 at 1:34 PM, Gary Gregory 
> wrote:
>
>> This is with Maven 3.3.9 though.
>>
>> Gary
>>
>> On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:
>>
>>> Does it have a dependency on log4j-core:test? It should. Could be a bug
>>> in your beta version of Maven ;)
>>>
>>> On 7 April 2017 at 14:46, Gary Gregory  wrote:
>>>
 Hi All:

 I'm seeing this in master:

 [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @
 log4j-1.2-api ---
 [INFO]
 [INFO] --- maven-resources-plugin:3.0.1:testResources
 (default-testResources) @ log4j-1.2-api ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 71 resources
 [INFO] Copying 3 resources
 [INFO] Copying 3 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:3.6.0:testCompile
 (default-testCompile) @ log4j-1.2-api ---
 [INFO] Changes detected - recompiling the module!
 [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
 ing-log4j2\log4j-1.2-api\target\test-classes
 [INFO] -
 [WARN] COMPILATION WARNING :
 [INFO] -
 [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
 [deprecation] setContextMap(Map) in Builder has been
 deprecated
 [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
 [deprecation] setContextMap(Map) in Builder has been
 deprecated
 [INFO] 2 warnings
 [INFO] -
 [INFO] -
 [ERROR] COMPILATION ERROR :
 [INFO] -
 [ERROR] warning: No processor claimed any of these annotations:
 org.junit.AfterClass,org.junit.Before,org.junit.runners.Para
 meterized.Parameters,org.junit.Rule,org.junit.ClassRule,org.
 junit.After,org.junit.runner.RunWith,org.junit.BeforeClass,o
 rg.junit.Test
 C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\LogWithMDCTest.java:[19,37] error: cannot
 find symbol
   symbol:   class LoggerContextRule
   location: package org.apache.logging.log4j.junit
 [ERROR] 

Re: Weird compilation error

[Matt Sicker]

It's already in the pom:
https://github.com/apache/logging-log4j2/blob/master/log4j-1.2-api/pom.xml#L74

I don't think it's scope=test, but type=test-jar.

On 7 April 2017 at 15:41, Gary Gregory  wrote:

> I added to log4j-1.2-api:
>
> 
>   org.apache.logging.log4j
>   log4j-core
>   test
>   test
> 
>
> but that blows up Maven 3.3.9:
>
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
> declaration of version (?) @ org.apache.logging.log4j:
> log4j-core-its:[unknown-version], C:\vcs\git\apache\logging\
> logging-log4j2\log4j-core-its\pom.xml, line 50, column 17
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.apache.logging.log4j:log4j-api:test-jar -> duplicate
> declaration of version (?) @ org.apache.logging.log4j:
> log4j-core-its:[unknown-version], C:\vcs\git\apache\logging\
> logging-log4j2\log4j-core-its\pom.xml, line 114, column 17
> [ERROR] 'dependencies.dependency.version' for 
> org.apache.logging.log4j:log4j-core:test
> is missing. @ org.apache.logging.log4j:log4j-1.2-api:[unknown-version],
> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\pom.xml, line 47,
> column 17
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
> declaration of version (?) @ org.apache.logging.log4j:
> log4j-slf4j-impl:[unknown-version], C:\vcs\git\apache\logging\
> logging-log4j2\log4j-slf4j-impl\pom.xml, line 70, column 17
> [WARNING] 'parent.relativePath' of POM 
> org.apache.logging.log4j:log4j-bom:2.8.3-SNAPSHOT
> (C:\vcs\git\apache\logging\logging-log4j2\log4j-bom\pom.xml) points at
> org.apache.logging.log4j:log4j instead of org.apache.logging:logging-parent,
> please verify your project structure @ line 19, column 11
>  @
>
>
> Gary
>
> On Fri, Apr 7, 2017 at 1:34 PM, Gary Gregory 
> wrote:
>
>> This is with Maven 3.3.9 though.
>>
>> Gary
>>
>> On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:
>>
>>> Does it have a dependency on log4j-core:test? It should. Could be a bug
>>> in your beta version of Maven ;)
>>>
>>> On 7 April 2017 at 14:46, Gary Gregory  wrote:
>>>
 Hi All:

 I'm seeing this in master:

 [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @
 log4j-1.2-api ---
 [INFO]
 [INFO] --- maven-resources-plugin:3.0.1:testResources
 (default-testResources) @ log4j-1.2-api ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 71 resources
 [INFO] Copying 3 resources
 [INFO] Copying 3 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:3.6.0:testCompile
 (default-testCompile) @ log4j-1.2-api ---
 [INFO] Changes detected - recompiling the module!
 [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
 ing-log4j2\log4j-1.2-api\target\test-classes
 [INFO] -
 [WARN] COMPILATION WARNING :
 [INFO] -
 [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
 [deprecation] setContextMap(Map) in Builder has been
 deprecated
 [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
 [deprecation] setContextMap(Map) in Builder has been
 deprecated
 [INFO] 2 warnings
 [INFO] -
 [INFO] -
 [ERROR] COMPILATION ERROR :
 [INFO] -
 [ERROR] warning: No processor claimed any of these annotations:
 org.junit.AfterClass,org.junit.Before,org.junit.runners.Para
 meterized.Parameters,org.junit.Rule,org.junit.ClassRule,org.
 junit.After,org.junit.runner.RunWith,org.junit.BeforeClass,o
 rg.junit.Test
 C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\LogWithMDCTest.java:[19,37] error: cannot
 find symbol
   symbol:   class LoggerContextRule
   location: package org.apache.logging.log4j.junit
 [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\LogWithMDCTest.java:[20,45] error: package
 org.apache.logging.log4j.test.appender does not exist
 [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\LogWithMDCTest.java:[36,24] error: cannot
 find symbol
   

Re: Weird compilation error

[Gary Gregory]

I added to log4j-1.2-api:


  org.apache.logging.log4j
  log4j-core
  test
  test


but that blows up Maven 3.3.9:

[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
declaration of version (?) @
org.apache.logging.log4j:log4j-core-its:[unknown-version],
C:\vcs\git\apache\logging\logging-log4j2\log4j-core-its\pom.xml, line 50,
column 17
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.apache.logging.log4j:log4j-api:test-jar -> duplicate
declaration of version (?) @
org.apache.logging.log4j:log4j-core-its:[unknown-version],
C:\vcs\git\apache\logging\logging-log4j2\log4j-core-its\pom.xml, line 114,
column 17
[ERROR] 'dependencies.dependency.version' for
org.apache.logging.log4j:log4j-core:test is missing. @
org.apache.logging.log4j:log4j-1.2-api:[unknown-version],
C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\pom.xml, line 47,
column 17
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.apache.logging.log4j:log4j-core:jar -> duplicate
declaration of version (?) @
org.apache.logging.log4j:log4j-slf4j-impl:[unknown-version],
C:\vcs\git\apache\logging\logging-log4j2\log4j-slf4j-impl\pom.xml, line 70,
column 17
[WARNING] 'parent.relativePath' of POM
org.apache.logging.log4j:log4j-bom:2.8.3-SNAPSHOT
(C:\vcs\git\apache\logging\logging-log4j2\log4j-bom\pom.xml) points at
org.apache.logging.log4j:log4j instead of
org.apache.logging:logging-parent, please verify your project structure @
line 19, column 11
 @


Gary

On Fri, Apr 7, 2017 at 1:34 PM, Gary Gregory  wrote:

> This is with Maven 3.3.9 though.
>
> Gary
>
> On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:
>
>> Does it have a dependency on log4j-core:test? It should. Could be a bug
>> in your beta version of Maven ;)
>>
>> On 7 April 2017 at 14:46, Gary Gregory  wrote:
>>
>>> Hi All:
>>>
>>> I'm seeing this in master:
>>>
>>> [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api
>>> ---
>>> [INFO]
>>> [INFO] --- maven-resources-plugin:3.0.1:testResources
>>> (default-testResources) @ log4j-1.2-api ---
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] Copying 71 resources
>>> [INFO] Copying 3 resources
>>> [INFO] Copying 3 resources
>>> [INFO]
>>> [INFO] --- maven-compiler-plugin:3.6.0:testCompile
>>> (default-testCompile) @ log4j-1.2-api ---
>>> [INFO] Changes detected - recompiling the module!
>>> [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
>>> ing-log4j2\log4j-1.2-api\target\test-classes
>>> [INFO] -
>>> [WARN] COMPILATION WARNING :
>>> [INFO] -
>>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
>>> [deprecation] setContextMap(Map) in Builder has been
>>> deprecated
>>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
>>> [deprecation] setContextMap(Map) in Builder has been
>>> deprecated
>>> [INFO] 2 warnings
>>> [INFO] -
>>> [INFO] -
>>> [ERROR] COMPILATION ERROR :
>>> [INFO] -
>>> [ERROR] warning: No processor claimed any of these annotations:
>>> org.junit.AfterClass,org.junit.Before,org.junit.runners.Para
>>> meterized.Parameters,org.junit.Rule,org.junit.ClassRule,org.
>>> junit.After,org.junit.runner.RunWith,org.junit.BeforeClass,
>>> org.junit.Test
>>> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\LogWithMDCTest.java:[19,37] error: cannot
>>> find symbol
>>>   symbol:   class LoggerContextRule
>>>   location: package org.apache.logging.log4j.junit
>>> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\LogWithMDCTest.java:[20,45] error: package
>>> org.apache.logging.log4j.test.appender does not exist
>>> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\LogWithMDCTest.java:[36,24] error: cannot
>>> find symbol
>>>   symbol:   class LoggerContextRule
>>>   location: class LogWithMDCTest
>>>
>>> Any thoughts?
>>>
>>> Gary
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> 
>>>
>>> 

Re: Weird compilation error

[Matt Sicker]

Maybe it's because it's a new snapshot version and you need to run "mvn
install" at least once?

On 7 April 2017 at 15:40, Matt Sicker  wrote:

> This is the first I've ever seen that error, and it's not popping up in
> Jenkins or anything. I don't think the code has changed since 2.8.2, so I
> don't know why it would break.
>
> On 7 April 2017 at 15:34, Gary Gregory  wrote:
>
>> This is with Maven 3.3.9 though.
>>
>> Gary
>>
>> On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:
>>
>>> Does it have a dependency on log4j-core:test? It should. Could be a bug
>>> in your beta version of Maven ;)
>>>
>>> On 7 April 2017 at 14:46, Gary Gregory  wrote:
>>>
 Hi All:

 I'm seeing this in master:

 [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @
 log4j-1.2-api ---
 [INFO]
 [INFO] --- maven-resources-plugin:3.0.1:testResources
 (default-testResources) @ log4j-1.2-api ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] Copying 71 resources
 [INFO] Copying 3 resources
 [INFO] Copying 3 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:3.6.0:testCompile
 (default-testCompile) @ log4j-1.2-api ---
 [INFO] Changes detected - recompiling the module!
 [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
 ing-log4j2\log4j-1.2-api\target\test-classes
 [INFO] -
 [WARN] COMPILATION WARNING :
 [INFO] -
 [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
 [deprecation] setContextMap(Map) in Builder has been
 deprecated
 [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
 [deprecation] setContextMap(Map) in Builder has been
 deprecated
 [INFO] 2 warnings
 [INFO] -
 [INFO] -
 [ERROR] COMPILATION ERROR :
 [INFO] -
 [ERROR] warning: No processor claimed any of these annotations:
 org.junit.AfterClass,org.junit.Before,org.junit.runners.Para
 meterized.Parameters,org.junit.Rule,org.junit.ClassRule,org.
 junit.After,org.junit.runner.RunWith,org.junit.BeforeClass,o
 rg.junit.Test
 C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\LogWithMDCTest.java:[19,37] error: cannot
 find symbol
   symbol:   class LoggerContextRule
   location: package org.apache.logging.log4j.junit
 [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\LogWithMDCTest.java:[20,45] error: package
 org.apache.logging.log4j.test.appender does not exist
 [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
 est\java\org\apache\log4j\LogWithMDCTest.java:[36,24] error: cannot
 find symbol
   symbol:   class LoggerContextRule
   location: class LogWithMDCTest

 Any thoughts?

 Gary

 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 Java Persistence with Hibernate, Second Edition
 

 
 JUnit in Action, Second Edition
 

 
 Spring Batch in Action
 
 
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory

>>>
>>>
>>>
>>> --
>>> Matt Sicker 
>>>
>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 

Re: Weird compilation error

[Matt Sicker]

This is the first I've ever seen that error, and it's not popping up in
Jenkins or anything. I don't think the code has changed since 2.8.2, so I
don't know why it would break.

On 7 April 2017 at 15:34, Gary Gregory  wrote:

> This is with Maven 3.3.9 though.
>
> Gary
>
> On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:
>
>> Does it have a dependency on log4j-core:test? It should. Could be a bug
>> in your beta version of Maven ;)
>>
>> On 7 April 2017 at 14:46, Gary Gregory  wrote:
>>
>>> Hi All:
>>>
>>> I'm seeing this in master:
>>>
>>> [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api
>>> ---
>>> [INFO]
>>> [INFO] --- maven-resources-plugin:3.0.1:testResources
>>> (default-testResources) @ log4j-1.2-api ---
>>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>>> [INFO] Copying 71 resources
>>> [INFO] Copying 3 resources
>>> [INFO] Copying 3 resources
>>> [INFO]
>>> [INFO] --- maven-compiler-plugin:3.6.0:testCompile
>>> (default-testCompile) @ log4j-1.2-api ---
>>> [INFO] Changes detected - recompiling the module!
>>> [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
>>> ing-log4j2\log4j-1.2-api\target\test-classes
>>> [INFO] -
>>> [WARN] COMPILATION WARNING :
>>> [INFO] -
>>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
>>> [deprecation] setContextMap(Map) in Builder has been
>>> deprecated
>>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
>>> [deprecation] setContextMap(Map) in Builder has been
>>> deprecated
>>> [INFO] 2 warnings
>>> [INFO] -
>>> [INFO] -
>>> [ERROR] COMPILATION ERROR :
>>> [INFO] -
>>> [ERROR] warning: No processor claimed any of these annotations:
>>> org.junit.AfterClass,org.junit.Before,org.junit.runners.Para
>>> meterized.Parameters,org.junit.Rule,org.junit.ClassRule,org.
>>> junit.After,org.junit.runner.RunWith,org.junit.BeforeClass,
>>> org.junit.Test
>>> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\LogWithMDCTest.java:[19,37] error: cannot
>>> find symbol
>>>   symbol:   class LoggerContextRule
>>>   location: package org.apache.logging.log4j.junit
>>> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\LogWithMDCTest.java:[20,45] error: package
>>> org.apache.logging.log4j.test.appender does not exist
>>> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\t
>>> est\java\org\apache\log4j\LogWithMDCTest.java:[36,24] error: cannot
>>> find symbol
>>>   symbol:   class LoggerContextRule
>>>   location: class LogWithMDCTest
>>>
>>> Any thoughts?
>>>
>>> Gary
>>>
>>> --
>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> 
>>>
>>> 
>>> JUnit in Action, Second Edition
>>> 
>>>
>>> 
>>> Spring Batch in Action
>>> 
>>> 
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
>
> 
> JUnit in Action, Second Edition
> 
>
> 
> Spring Batch in Action
> 

Re: Weird compilation error

[Gary Gregory]

This is with Maven 3.3.9 though.

Gary

On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker  wrote:

> Does it have a dependency on log4j-core:test? It should. Could be a bug in
> your beta version of Maven ;)
>
> On 7 April 2017 at 14:46, Gary Gregory  wrote:
>
>> Hi All:
>>
>> I'm seeing this in master:
>>
>> [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api
>> ---
>> [INFO]
>> [INFO] --- maven-resources-plugin:3.0.1:testResources
>> (default-testResources) @ log4j-1.2-api ---
>> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>> [INFO] Copying 71 resources
>> [INFO] Copying 3 resources
>> [INFO] Copying 3 resources
>> [INFO]
>> [INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile)
>> @ log4j-1.2-api ---
>> [INFO] Changes detected - recompiling the module!
>> [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\logg
>> ing-log4j2\log4j-1.2-api\target\test-classes
>> [INFO] -
>> [WARN] COMPILATION WARNING :
>> [INFO] -
>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\
>> test\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
>> [deprecation] setContextMap(Map) in Builder has been
>> deprecated
>> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\
>> test\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
>> [deprecation] setContextMap(Map) in Builder has been
>> deprecated
>> [INFO] 2 warnings
>> [INFO] -
>> [INFO] -
>> [ERROR] COMPILATION ERROR :
>> [INFO] -
>> [ERROR] warning: No processor claimed any of these annotations:
>> org.junit.AfterClass,org.junit.Before,org.junit.runners.
>> Parameterized.Parameters,org.junit.Rule,org.junit.
>> ClassRule,org.junit.After,org.junit.runner.RunWith,org.
>> junit.BeforeClass,org.junit.Test
>> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\
>> test\java\org\apache\log4j\LogWithMDCTest.java:[19,37] error: cannot
>> find symbol
>>   symbol:   class LoggerContextRule
>>   location: package org.apache.logging.log4j.junit
>> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\
>> test\java\org\apache\log4j\LogWithMDCTest.java:[20,45] error: package
>> org.apache.logging.log4j.test.appender does not exist
>> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\
>> test\java\org\apache\log4j\LogWithMDCTest.java:[36,24] error: cannot
>> find symbol
>>   symbol:   class LoggerContextRule
>>   location: class LogWithMDCTest
>>
>> Any thoughts?
>>
>> Gary
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 
>>
>> 
>> Spring Batch in Action
>> 
>> 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> Matt Sicker 
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Weird compilation error

[Matt Sicker]

Does it have a dependency on log4j-core:test? It should. Could be a bug in
your beta version of Maven ;)

On 7 April 2017 at 14:46, Gary Gregory  wrote:

> Hi All:
>
> I'm seeing this in master:
>
> [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api
> ---
> [INFO]
> [INFO] --- maven-resources-plugin:3.0.1:testResources
> (default-testResources) @ log4j-1.2-api ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 71 resources
> [INFO] Copying 3 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile)
> @ log4j-1.2-api ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 20 source files to C:\vcs\git\apache\logging\
> logging-log4j2\log4j-1.2-api\target\test-classes
> [INFO] -
> [WARN] COMPILATION WARNING :
> [INFO] -
> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\
> src\test\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
> [deprecation] setContextMap(Map) in Builder has been
> deprecated
> [WARN] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\
> src\test\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
> [deprecation] setContextMap(Map) in Builder has been
> deprecated
> [INFO] 2 warnings
> [INFO] -
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR] warning: No processor claimed any of these annotations:
> org.junit.AfterClass,org.junit.Before,org.junit.runners.Parameterized.
> Parameters,org.junit.Rule,org.junit.ClassRule,org.junit.
> After,org.junit.runner.RunWith,org.junit.BeforeClass,org.junit.Test
> C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\
> src\test\java\org\apache\log4j\LogWithMDCTest.java:[19,37] error: cannot
> find symbol
>   symbol:   class LoggerContextRule
>   location: package org.apache.logging.log4j.junit
> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\
> src\test\java\org\apache\log4j\LogWithMDCTest.java:[20,45] error: package
> org.apache.logging.log4j.test.appender does not exist
> [ERROR] C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\
> src\test\java\org\apache\log4j\LogWithMDCTest.java:[36,24] error: cannot
> find symbol
>   symbol:   class LoggerContextRule
>   location: class LogWithMDCTest
>
> Any thoughts?
>
> Gary
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
>
> 
> JUnit in Action, Second Edition
> 
>
> 
> Spring Batch in Action
> 
> 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker 

Weird compilation error

[Gary Gregory]

Hi All:

I'm seeing this in master:

[INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api ---
[INFO]
[INFO] --- maven-resources-plugin:3.0.1:testResources
(default-testResources) @ log4j-1.2-api ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 71 resources
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile) @
log4j-1.2-api ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 20 source files to
C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\target\test-classes
[INFO] -
[WARN] COMPILATION WARNING :
[INFO] -
[WARN]
C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\test\java\org\apache\log4j\layout\Log4j1XmlLayoutTest.java:[66,16]
[deprecation] setContextMap(Map) in Builder has been
deprecated
[WARN]
C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\test\java\org\apache\log4j\pattern\Log4j1MdcPatternConverterTest.java:[70,16]
[deprecation] setContextMap(Map) in Builder has been
deprecated
[INFO] 2 warnings
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] warning: No processor claimed any of these annotations:
org.junit.AfterClass,org.junit.Before,org.junit.runners.Parameterized.Parameters,org.junit.Rule,org.junit.ClassRule,org.junit.After,org.junit.runner.RunWith,org.junit.BeforeClass,org.junit.Test
C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\test\java\org\apache\log4j\LogWithMDCTest.java:[19,37]
error: cannot find symbol
  symbol:   class LoggerContextRule
  location: package org.apache.logging.log4j.junit
[ERROR]
C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\test\java\org\apache\log4j\LogWithMDCTest.java:[20,45]
error: package org.apache.logging.log4j.test.appender does not exist
[ERROR]
C:\vcs\git\apache\logging\logging-log4j2\log4j-1.2-api\src\test\java\org\apache\log4j\LogWithMDCTest.java:[36,24]
error: cannot find symbol
  symbol:   class LoggerContextRule
  location: class LogWithMDCTest

Any thoughts?

Gary

-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Yet another logging facade

[Ralph Goers]

See 
http://stackoverflow.com/questions/41633278/can-we-use-all-features-of-log4j2-if-we-use-it-along-with-slf4j-api/41635246#41635246
 
.
 Note that item 10 on this list was recently fixed.

Ralph


> On Apr 7, 2017, at 12:04 PM, Ralph Goers  wrote:
> 
> I just took a look at the list. I don’t see the response that points to 
> bugzilla.
> 
> In your comment you mentioned that Log4j provides an api but you didn’t list 
> the reasons why it is better. Remko posted a stack overflow post that has 10 
> reasons why it is better.  But more importantly, users have been asking for 
> enhancements to the SLF4J API for quite a while. Eventually the API is going 
> to have to be enhanced. How is OSGi going to accommodate for that?
> 
> Ralph
> 
>> On Apr 7, 2017, at 9:40 AM, Matt Sicker > > wrote:
>> 
>> I got a response on the mailing list. There's a public bugzilla we can 
>> comment on apparently which is linked in the PDF.
>> 
>> On 6 April 2017 at 20:02, Matt Sicker > > wrote:
>> I'm not sure where they develop the standards, but there's an osgi-dev 
>> mailing list (where I found this posted today): 
>> https://www.osgi.org/community/mail-lists/ 
>> 
>> 
>> I don't see Apache on this list despite being the foundation behind most of 
>> the open source OSGi projects out there: 
>> https://www.osgi.org/about-us/members/ 
>> 
>> 
>> However, there are many companies on that list who directly contribute to 
>> said Apache projects.
>> 
>> I can't find any info on their site about how to offer feedback. This is 
>> just as (if not more) convoluted than the JCP.
>> 
>> On 6 April 2017 at 19:41, Gary Gregory > > wrote:
>> A quick review of the document appears to have SLF4J as a requirement. Shame 
>> about that. 
>> 
>> Gary
>> 
>> On Thu, Apr 6, 2017 at 5:34 PM, Ralph Goers > > wrote:
>> Where does one comment on these?
>> 
>> The problem is that they mention Java 8 support, but SLF4J doesn’t take 
>> advantage of any Java 8 features yet. No support for Lamda’s.  From what I 
>> am seeing the next release will support running in Java 9 and will leverage 
>> StackWalker and support Java modules but Ceki hasn’t mentioned if he is 
>> going to add to the API to support things users have been asking for.
>> 
>> I’d hate to see them base their standard on what was then the current 
>> release of SLF4J and then for it to be enhanced and they are stuck with a 
>> limited API.
>> 
>> I wonder how much input, if any, Ceki had in this.  
>> 
>> As a side note, he also changed the binding mechanism and I am not sure if 
>> it is backward compatible, soI have a feeling log4j-slf4j-impl will need 
>> changes to support that version. 
>> 
>> Ralph
>> 
>> 
>>> On Apr 6, 2017, at 4:00 PM, Remko Popma >> > wrote:
>>> 
>>> Good find. I noticed that the document points to Apache Sling and says 
>>> "uses the most common parts today used for logging: SLF4J for clients and 
>>> logback for processing."  Seems like Sling decided that in 2013 and never 
>>> looked back. Which is fine, but I believe Log4j2 has changed the landscape 
>>> the last 4 years. 
>>> 
>>> Sent from my iPhone
>>> 
>>> On Apr 7, 2017, at 6:08, Matt Sicker >> > wrote:
>>> 
 OSGi is looking at updating their logging API:
 
 https://github.com/osgi/design/blob/master/rfcs/rfc0219/rfc-0219-LogService-Update.pdf
  
 
 
 We might want to provide feedback.
 
 -- 
 Matt Sicker >
>> 
>> 
>> 
>> 
>> -- 
>> E-Mail: garydgreg...@gmail.com  | 
>> ggreg...@apache.org  
>> Java Persistence with Hibernate, Second Edition 
>> 
>>   
>> 
>> JUnit in Action, Second Edition 
>> 
>>   
>> 
>> Spring Batch in Action 
>> 
>>   

Re: Yet another logging facade

[Ralph Goers]

I just took a look at the list. I don’t see the response that points to 
bugzilla.

In your comment you mentioned that Log4j provides an api but you didn’t list 
the reasons why it is better. Remko posted a stack overflow post that has 10 
reasons why it is better.  But more importantly, users have been asking for 
enhancements to the SLF4J API for quite a while. Eventually the API is going to 
have to be enhanced. How is OSGi going to accommodate for that?

Ralph

> On Apr 7, 2017, at 9:40 AM, Matt Sicker  wrote:
> 
> I got a response on the mailing list. There's a public bugzilla we can 
> comment on apparently which is linked in the PDF.
> 
> On 6 April 2017 at 20:02, Matt Sicker  > wrote:
> I'm not sure where they develop the standards, but there's an osgi-dev 
> mailing list (where I found this posted today): 
> https://www.osgi.org/community/mail-lists/ 
> 
> 
> I don't see Apache on this list despite being the foundation behind most of 
> the open source OSGi projects out there: 
> https://www.osgi.org/about-us/members/ 
> 
> 
> However, there are many companies on that list who directly contribute to 
> said Apache projects.
> 
> I can't find any info on their site about how to offer feedback. This is just 
> as (if not more) convoluted than the JCP.
> 
> On 6 April 2017 at 19:41, Gary Gregory  > wrote:
> A quick review of the document appears to have SLF4J as a requirement. Shame 
> about that. 
> 
> Gary
> 
> On Thu, Apr 6, 2017 at 5:34 PM, Ralph Goers  > wrote:
> Where does one comment on these?
> 
> The problem is that they mention Java 8 support, but SLF4J doesn’t take 
> advantage of any Java 8 features yet. No support for Lamda’s.  From what I am 
> seeing the next release will support running in Java 9 and will leverage 
> StackWalker and support Java modules but Ceki hasn’t mentioned if he is going 
> to add to the API to support things users have been asking for.
> 
> I’d hate to see them base their standard on what was then the current release 
> of SLF4J and then for it to be enhanced and they are stuck with a limited API.
> 
> I wonder how much input, if any, Ceki had in this.  
> 
> As a side note, he also changed the binding mechanism and I am not sure if it 
> is backward compatible, soI have a feeling log4j-slf4j-impl will need changes 
> to support that version. 
> 
> Ralph
> 
> 
>> On Apr 6, 2017, at 4:00 PM, Remko Popma > > wrote:
>> 
>> Good find. I noticed that the document points to Apache Sling and says "uses 
>> the most common parts today used for logging: SLF4J for clients and logback 
>> for processing."  Seems like Sling decided that in 2013 and never looked 
>> back. Which is fine, but I believe Log4j2 has changed the landscape the last 
>> 4 years. 
>> 
>> Sent from my iPhone
>> 
>> On Apr 7, 2017, at 6:08, Matt Sicker > > wrote:
>> 
>>> OSGi is looking at updating their logging API:
>>> 
>>> https://github.com/osgi/design/blob/master/rfcs/rfc0219/rfc-0219-LogService-Update.pdf
>>>  
>>> 
>>> 
>>> We might want to provide feedback.
>>> 
>>> -- 
>>> Matt Sicker >
> 
> 
> 
> 
> -- 
> E-Mail: garydgreg...@gmail.com  | 
> ggreg...@apache.org  
> Java Persistence with Hibernate, Second Edition 
> 
>   
> 
> JUnit in Action, Second Edition 
> 
>   
> 
> Spring Batch in Action 
> 
>   
> 
> Blog: http://garygregory.wordpress.com  
> Home: http://garygregory.com/ 
> Tweet! http://twitter.com/GaryGregory 
> 
> 
> -- 
> Matt Sicker >
> 
> 
> 
> -- 
> Matt Sicker >

Re: Yet another logging facade

[Matt Sicker]

I got a response on the mailing list. There's a public bugzilla we can
comment on apparently which is linked in the PDF.

On 6 April 2017 at 20:02, Matt Sicker  wrote:

> I'm not sure where they develop the standards, but there's an osgi-dev
> mailing list (where I found this posted today): https://www.osgi.org/
> community/mail-lists/
>
> I don't see Apache on this list despite being the foundation behind most
> of the open source OSGi projects out there: https://www.osgi.org/
> about-us/members/
>
> However, there are many companies on that list who directly contribute to
> said Apache projects.
>
> I can't find any info on their site about how to offer feedback. This is
> just as (if not more) convoluted than the JCP.
>
> On 6 April 2017 at 19:41, Gary Gregory  wrote:
>
>> A quick review of the document appears to have SLF4J as a requirement.
>> Shame about that.
>>
>> Gary
>>
>> On Thu, Apr 6, 2017 at 5:34 PM, Ralph Goers 
>> wrote:
>>
>>> Where does one comment on these?
>>>
>>> The problem is that they mention Java 8 support, but SLF4J doesn’t take
>>> advantage of any Java 8 features yet. No support for Lamda’s.  >From what I
>>> am seeing the next release will support running in Java 9 and will leverage
>>> StackWalker and support Java modules but Ceki hasn’t mentioned if he is
>>> going to add to the API to support things users have been asking for.
>>>
>>> I’d hate to see them base their standard on what was then the current
>>> release of SLF4J and then for it to be enhanced and they are stuck with a
>>> limited API.
>>>
>>> I wonder how much input, if any, Ceki had in this.
>>>
>>> As a side note, he also changed the binding mechanism and I am not sure
>>> if it is backward compatible, soI have a feeling log4j-slf4j-impl will need
>>> changes to support that version.
>>>
>>> Ralph
>>>
>>>
>>> On Apr 6, 2017, at 4:00 PM, Remko Popma  wrote:
>>>
>>> Good find. I noticed that the document points to Apache Sling and says
>>> "uses the most common parts today used for logging: SLF4J for clients and
>>> logback for processing."  Seems like Sling decided that in 2013 and never
>>> looked back. Which is fine, but I believe Log4j2 has changed the landscape
>>> the last 4 years.
>>>
>>> Sent from my iPhone
>>>
>>> On Apr 7, 2017, at 6:08, Matt Sicker  wrote:
>>>
>>> OSGi is looking at updating their logging API:
>>>
>>> https://github.com/osgi/design/blob/master/rfcs/rfc0219/rfc-
>>> 0219-LogService-Update.pdf
>>>
>>> We might want to provide feedback.
>>>
>>> --
>>> Matt Sicker 
>>>
>>>
>>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 
>>
>> 
>> Spring Batch in Action
>> 
>> 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> Matt Sicker 
>



-- 
Matt Sicker 

Re: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0

[Ralph Goers]

We will have to modify log4j-slf4j-impl to support the new binding mechanism. I 
know it uses service loader but I haven’t looked at the details. I looked at 
service loader when I created the binding between our api and core but decided 
not to use it because I wanted to also include the logic to match API versions. 
So what we have is something similar to service loader but it doesn’t use it.

Ralph

> On Apr 7, 2017, at 8:07 AM, Matt Sicker  wrote:
> 
> So how shall we go about handling this?
> 
> -- Forwarded message --
> From: QOS.ch annoucements >
> Date: 7 April 2017 at 05:46
> Subject: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0
> To: annou...@qos.ch 
> 
> 
> 
> Java 9 modularization
> =
> 
> I  am  pleased  to  announce SLF4J  1.8.0-alpha0,  a  modularized
> version of  slf4j compatible  with Java 9  and in  particular its
> Java Platform Module System (JSR 376), a.k.a project Jigsaw.
> 
> Although there are  no client facing API  changes in 1.8.0-alpha0
> release, the static binding mechanism has been abandoned in favor
> of java.util.ServiceLoader introduced in  Java 6. It follows that
> slf4j-api  now requires  Java 6.  Just as  importantly, slf4j-api
> version 1.8.x  will no  longer search for  the StaticLoggerBinder
> class.
> 
> Instead of  "bindings" now slf4j-api looks  for "providers" which
> ship   withslf4j-nop-1.8.x.jar,   slf4j-simple-1.8.x.jar   or
> slf4j-jdk14-1.8.x.jar.
> 
> Given that in some environments, it is not possible to modify the
> version  of  slf4j-api,  slf4j  1.8.x  "providers"  also  act  as
> 1.7.x/1.6.x "bindings".
> 
> For   example,  having   slf4j-api-1.8.x.jar  and
> slf4j-simple-1.7.x.jar on  the class path will  NOT work, whereas
> having  slf4j-api-1.7.x.jar  and  slf4j-simple-1.8.x.jar  on  the
> class path will work fine.
> 
> In other words:
> 
> slf4j-api-1.8.x.jar + slf4j-simple-1.7.x.jar ==> "No SLF4J
> providers found" warning
> 
> whereas:
> 
> slf4j-api-1.7.x.jar + slf4j-simple-1.8.x.jar ==> OK
> 
> 
> Download
> 
> 
> The relevant artifacts can be obtained via the Maven central
> repository.
> 
> OSGi changes
> 
> 
> While  we expect  the changes  introduced in  SLF4J 1.8.x  to be
> rather   transparent   to   users,   given   JPMS   restrictions,
> implementations had to be moved from the org.slf4.impl package to
> packages  specific  to  each  provider.  Consequently,  the  OSGi
> declarations in MANIFEST.MF files had  to be modified.  Our tests
> indicate  that   SLF4J  version  1.8.x  should   work  fine  with
> OSGi. However, more in depth testing  is in order. We are looking
> for volunteers for such tests.
> 
> 
> The slf4j-log4j12 module
> 
> 
> Due to technical reasons,  slf4j-log4j12 could not be modularized
> in  this alpha0  release. However,  we expect  the problem  to be
> solved in future 1.8.x releases.
> 
> 
> Announcement mailing list
> =
> 
> You can receive SLF4J related announcements by subscribing to the
> SLF4J announce mailing list. To subscribe to QOS.ch announce list,
> please visit the following URL.
> 
>http://www.qos.ch/mailman/listinfo/announce 
> 
> 
> You may also receive announcements via twitter:
> 
>https://twitter.com/qos_ch 
> 
> Enjoy,
> 
> -- 
> Ceki Gülcü
> ___
> announce mailing list
> annou...@qos.ch 
> http://mailman.qos.ch/mailman/listinfo/announce 
> 
> 
> 
> -- 
> Matt Sicker >

Fwd: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0

[Matt Sicker]

So how shall we go about handling this?

-- Forwarded message --
From: QOS.ch annoucements 
Date: 7 April 2017 at 05:46
Subject: [qos.ch-announce] Release of SLF4J version 1.8.0-alpha0
To: annou...@qos.ch



Java 9 modularization
=

I  am  pleased  to  announce SLF4J  1.8.0-alpha0,  a  modularized
version of  slf4j compatible  with Java 9  and in  particular its
Java Platform Module System (JSR 376), a.k.a project Jigsaw.

Although there are  no client facing API  changes in 1.8.0-alpha0
release, the static binding mechanism has been abandoned in favor
of java.util.ServiceLoader introduced in  Java 6. It follows that
slf4j-api  now requires  Java 6.  Just as  importantly, slf4j-api
version 1.8.x  will no  longer search for  the StaticLoggerBinder
class.

Instead of  "bindings" now slf4j-api looks  for "providers" which
ship   withslf4j-nop-1.8.x.jar,   slf4j-simple-1.8.x.jar   or
slf4j-jdk14-1.8.x.jar.

Given that in some environments, it is not possible to modify the
version  of  slf4j-api,  slf4j  1.8.x  "providers"  also  act  as
1.7.x/1.6.x "bindings".

For   example,  having   slf4j-api-1.8.x.jar  and
slf4j-simple-1.7.x.jar on  the class path will  NOT work, whereas
having  slf4j-api-1.7.x.jar  and  slf4j-simple-1.8.x.jar  on  the
class path will work fine.

In other words:

slf4j-api-1.8.x.jar + slf4j-simple-1.7.x.jar ==> "No SLF4J
providers found" warning

whereas:

slf4j-api-1.7.x.jar + slf4j-simple-1.8.x.jar ==> OK


Download


The relevant artifacts can be obtained via the Maven central
repository.

OSGi changes


While  we expect  the changes  introduced in  SLF4J 1.8.x  to be
rather   transparent   to   users,   given   JPMS   restrictions,
implementations had to be moved from the org.slf4.impl package to
packages  specific  to  each  provider.  Consequently,  the  OSGi
declarations in MANIFEST.MF files had  to be modified.  Our tests
indicate  that   SLF4J  version  1.8.x  should   work  fine  with
OSGi. However, more in depth testing  is in order. We are looking
for volunteers for such tests.


The slf4j-log4j12 module


Due to technical reasons,  slf4j-log4j12 could not be modularized
in  this alpha0  release. However,  we expect  the problem  to be
solved in future 1.8.x releases.


Announcement mailing list
=

You can receive SLF4J related announcements by subscribing to the
SLF4J announce mailing list. To subscribe to QOS.ch announce list,
please visit the following URL.

   http://www.qos.ch/mailman/listinfo/announce

You may also receive announcements via twitter:

   https://twitter.com/qos_ch

Enjoy,

-- 
Ceki Gülcü
___
announce mailing list
annou...@qos.ch
http://mailman.qos.ch/mailman/listinfo/announce



-- 
Matt Sicker 

JDK 9 Developer Preview is now available on java.net

[Rory O'Donnell]

Hi Nick,


 *JDK 9 Developer Preview is now available on java.net [1]
 *

Developer Preview milestone: - A reasonably stable build suitable for 
broad testing by the developer community is available.

JDK 9 Builds 163 and higher include all planned features.


*Attention annotation processing users and authors - * Request for 
feedback on annotation processing API changes made in JDK 9.


As has been done previously during Java SE 7 and Java SE 8, the JSR 269 
annotation processing API is undergoing a maintenance review (MR) as 
part of Java SE 9. Details of the changes in JDK 9 Early Access build 
163 & build 164 available here [2]


Please report experiences running processors under JDK 9 and feedback on 
the API changes to the compiler-dev mailing list.
(If you haven’t already subscribed to that list then please do so first, 
otherwise your message will be discarded as spam.)



Rgds, Rory

[1] https://jdk9.java.net/download/
[2] 
http://mail.openjdk.java.net/pipermail/compiler-dev/2017-April/010896.html


--
Rgds,Rory O'Donnell
Quality Engineering Manager