Re: Jenkins and Maven 3.5.0

[Gary Gregory]

Sure, why not? Let's eat our own Apache dog food. Fresh too!

Gary

On Apr 8, 2017 5:44 PM, "Matt Sicker"  wrote:

> Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it
> make sense to switch to it there? I know in theory everything seems to work
> with any version of Maven 3.x, but I'm also wondering if it's worth setting
> up Jenkins like we did for Windows with multiple versions to catch any
> strange build issues sooner rather than later.
>
> --
> Matt Sicker 
>

Jenkins and Maven 3.5.0

[Matt Sicker]

Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it
make sense to switch to it there? I know in theory everything seems to work
with any version of Maven 3.x, but I'm also wondering if it's worth setting
up Jenkins like we did for Windows with multiple versions to catch any
strange build issues sooner rather than later.

-- 
Matt Sicker 

Re: [ANN] Log4j 2.8.2 released

[Remko Popma]

Blogged: https://blogs.apache.org/logging/entry/log4j-2-8-2-released

On Sun, Apr 9, 2017 at 1:53 AM, Matt Sicker  wrote:

> The Apache Log4j 2 team is pleased to announce the Log4j 2.8.2 release!
>
> Apache Log4j is a well known framework for logging application behavior.
> Log4j 2 is an upgrade to Log4j that provides significant improvements over
> its predecessor, Log4j 1.x, and provides many other modern features such as
> support for Markers, lambda expressions for lazy logging, property
> substitution using Lookups, multiple patterns on a PatternLayout and
> asynchronous Loggers. Another notable Log4j 2 feature is the ability to be
> "garbage-free" (avoid allocating temporary objects) while logging. In
> addition, Log4j 2 will not lose events while reconfiguring.
>
> This release primarily contains bugfixes and minor enhancements. More
> details on the new features and fixes are itemized below.
>
> Note that subsequent to the 2.6 release a minor source incompatibility was
> found due to the addition of new methods to the Logger interface. If you
> have code that does:
>
> logger.error(null, “This is the log message”, throwable);
>
> or similar with any log level you will get a compiler error saying the
> reference is ambiguous. To correct this either do:
>
> logger.error(“This is the log message”, throwable);
>
> or
>
> logger.error((Marker) null, “This is the log message”, throwable);
>
> The Log4j 2.8.2 API, as well as many core components, maintains binary
> compatibility with previous releases.
>
> GA
> Release 2.8.2
>
> Changes in this version include:
>
> New
> Features
>
>- LOG4J2-1863 : Add
>support for filtering input in TcpSocketServer and UdpSocketServer.
>- LOG4J2-1848 : Add
>JSON encoding support to EncodingPatternConverter %encode{}.
>- LOG4J2-1843 : Add
>support for appending common suffix to each line of throwable stack trace.
>Thanks to Zilong Song.
>- LOG4J2-1838 : Add
>support for appending common suffix to each line of extended and root
>throwable stack trace. Thanks to Zilong Song.
>
>
> Fixed
> Bugs
>
>- LOG4J2-1861 : Fix
>JavaDoc on org.apache.logging.log4j.ThreadContext about inheritance.
>- LOG4J2-1862 : Fix
>JavaDoc about @Order and OrderComparator ordering. Thanks to wangyuntao.
>- LOG4J2-1849 :
>Fixed daylight savings time issue with FixedDateFormat.
>- LOG4J2-1850 : Fix
>CassandraRule and unit tests on Windows. Thanks to Ludovic Hochet.
>- LOG4J2-1840 : Fix
>typo in %replace converter documentation. Thanks to Pradeep Balasundaram.
>- LOG4J2-1846 :
>Handle when LogEvent.getLoggerName() returns null in
>LoggerNameLevelRewritePolicy.
>- LOG4J2-1845 :
>Handle when LogEvent.getLoggerName() returns null in KafkaAppender.
>- LOG4J2-1853 : The
>default value of RandomAccessFileAppender.Builder append field is
>wrong. Thanks to wangyuntao.
>- LOG4J2-1835 : Fix
>documentation about the licensing for JeroMQ.
>- LOG4J2-1836 :
>Update the API version to 2.6.0.
>- LOG4J2-1831 :
>NullPointerException in HtmlLayout. Thanks to Edward Serebrinskiy.
>- LOG4J2-1820 :
>Log4j 2.8 can lose exceptions when a security manager is present. Thanks to
>Jason Tedor.
>
>
> 
> Changes
>
>- LOG4J2-1827 :
>Move integration tests to their own module to speed up build.
>- LOG4J2-1856 :
>Update Jackson from 2.8.6 to 2.8.7.
>
> --
>
> Apache Log4j 2.8.2 requires a minimum of Java 7 to build and run. Log4j
> 2.3 was the last release that supported Java 6.
>
> Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api
> component, however it does not implement 

[jira] [Created] (LOG4J2-1871) Add an Avro layout for extensible binary encoding

[Matt Sicker (JIRA)]

Matt Sicker created LOG4J2-1871:
---

 Summary: Add an Avro layout for extensible binary encoding
 Key: LOG4J2-1871
 URL: https://issues.apache.org/jira/browse/LOG4J2-1871
 Project: Log4j 2
  Issue Type: New Feature
  Components: Layouts
Reporter: Matt Sicker


Similar in style to the JSON layout (and other related dynamic layouts), a new 
layout based on [Apache Avro|https://avro.apache.org/docs/current/] would be a 
good choice for simple binary layouts. Avro also provides adapters for Apache 
Thrift and Protobuf, so this library makes sense as a good choice for the most 
extensible binary layout. This also opens up the ability to create a socket 
appender or similar using the Avro IPC classes.



--
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-1870) Add a "fast defaults" option to make modern configurations simpler

[Matt Sicker (JIRA)]

Matt Sicker created LOG4J2-1870:
---

 Summary: Add a "fast defaults" option to make modern 
configurations simpler
 Key: LOG4J2-1870
 URL: https://issues.apache.org/jira/browse/LOG4J2-1870
 Project: Log4j 2
  Issue Type: New Feature
  Components: Core
Reporter: Matt Sicker


There have been a few non-default options added over various releases which 
improve the performance of Log4j. These include:

* Async loggers
* Direct console appender
* Async Kafka appender

This feature should add a Log4j system property to quickly enable fast defaults 
instead of the backward compatible ones. This should enable async loggers 
globally when the LMAX library is available. This should also enable current 
and future fast options to appenders and other plugins.

Ideally, this feature should be accompanied by an explanation of how to choose 
options and appenders for difference scenarios. For example, it would be great 
to explain why a user might use different wait strategies in different 
scenarios (high throughput versus low latency versus safety), or why using 
different clocks than the default can be useful. Explicit details of all 
available options should remain on their normal manual pages, but quick 
summaries and pointers on such a page would be useful.



--
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

[ANN] Log4j 2.8.2 released

[Matt Sicker]

The Apache Log4j 2 team is pleased to announce the Log4j 2.8.2 release!

Apache Log4j is a well known framework for logging application behavior.
Log4j 2 is an upgrade to Log4j that provides significant improvements over
its predecessor, Log4j 1.x, and provides many other modern features such as
support for Markers, lambda expressions for lazy logging, property
substitution using Lookups, multiple patterns on a PatternLayout and
asynchronous Loggers. Another notable Log4j 2 feature is the ability to be
"garbage-free" (avoid allocating temporary objects) while logging. In
addition, Log4j 2 will not lose events while reconfiguring.

This release primarily contains bugfixes and minor enhancements. More
details on the new features and fixes are itemized below.

Note that subsequent to the 2.6 release a minor source incompatibility was
found due to the addition of new methods to the Logger interface. If you
have code that does:

logger.error(null, “This is the log message”, throwable);

or similar with any log level you will get a compiler error saying the
reference is ambiguous. To correct this either do:

logger.error(“This is the log message”, throwable);

or

logger.error((Marker) null, “This is the log message”, throwable);

The Log4j 2.8.2 API, as well as many core components, maintains binary
compatibility with previous releases.
GA
Release 2.8.2

Changes in this version include:
New
Features

   - LOG4J2-1863 : Add
   support for filtering input in TcpSocketServer and UdpSocketServer.
   - LOG4J2-1848 : Add
   JSON encoding support to EncodingPatternConverter %encode{}.
   - LOG4J2-1843 : Add
   support for appending common suffix to each line of throwable stack trace.
   Thanks to Zilong Song.
   - LOG4J2-1838 : Add
   support for appending common suffix to each line of extended and root
   throwable stack trace. Thanks to Zilong Song.

Fixed
Bugs

   - LOG4J2-1861 : Fix
   JavaDoc on org.apache.logging.log4j.ThreadContext about inheritance.
   - LOG4J2-1862 : Fix
   JavaDoc about @Order and OrderComparator ordering. Thanks to wangyuntao.
   - LOG4J2-1849 : Fixed
   daylight savings time issue with FixedDateFormat.
   - LOG4J2-1850 : Fix
   CassandraRule and unit tests on Windows. Thanks to Ludovic Hochet.
   - LOG4J2-1840 : Fix
   typo in %replace converter documentation. Thanks to Pradeep Balasundaram.
   - LOG4J2-1846 :
   Handle when LogEvent.getLoggerName() returns null in
   LoggerNameLevelRewritePolicy.
   - LOG4J2-1845 :
   Handle when LogEvent.getLoggerName() returns null in KafkaAppender.
   - LOG4J2-1853 : The
   default value of RandomAccessFileAppender.Builder append field is wrong.
   Thanks to wangyuntao.
   - LOG4J2-1835 : Fix
   documentation about the licensing for JeroMQ.
   - LOG4J2-1836 :
   Update the API version to 2.6.0.
   - LOG4J2-1831 :
   NullPointerException in HtmlLayout. Thanks to Edward Serebrinskiy.
   - LOG4J2-1820 : Log4j
   2.8 can lose exceptions when a security manager is present. Thanks to Jason
   Tedor.


Changes

   - LOG4J2-1827 : Move
   integration tests to their own module to speed up build.
   - LOG4J2-1856 :
   Update Jackson from 2.8.6 to 2.8.7.

--

Apache Log4j 2.8.2 requires a minimum of Java 7 to build and run. Log4j 2.3
was the last release that supported Java 6.

Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api
component, however it does not implement some of the very implementation
specific classes and methods. The package names and Maven groupId have been
changed to org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how
to submit bug reports, patches, or suggestions for improvement, see 

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

[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