You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2017/01/17 16:04:21 UTC
Remaining tasks for a 2.8 release
I'm working on getting the Log4j Scala repo set up independently from the
main Log4j repo (and doing Log4j Boot on the side; this will be released
independently, so don't worry about this blocking anything) and doing some
general site cleanups and whatnot. For 2.8, the other non-core modules will
most likely remain where they are and the Log4j Scala API repo gets to be
our first foray into the separated repos space.
Feature-wise, are there any other things we'd like to complete before
cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
pain points of migrating config formats being brought up again, so it would
be great to get our Log4j 1 config support in this release, but that
depends on timing, too (we could always RERO and add it to the next release
if nobody has time to finish that feature).
--
Matt Sicker <bo...@gmail.com>
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
For Log4j 1 config support, we need to go through the Log4j 1 appenders and
see how to map them to Log4j 2 appenders, or reimplement in Log4j 2 if not
possible to map. See https://issues.apache.org/jira/browse/LOG4J2-1523
(Layouts are already done: https://issues.apache.org/jira/browse/LOG4J2-1522
)
On Wed, Jan 18, 2017 at 12:55 AM, Remko Popma <re...@gmail.com> wrote:
> I would like to do more on the Log4j 1 support but have been swamped at
> work. Should not be a showstopper for 2.8 though.
>
> Sent from my iPhone
>
> On Jan 18, 2017, at 4:11, Gary Gregory <ga...@gmail.com> wrote:
>
> On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <bo...@gmail.com> wrote:
>
>> I'm working on getting the Log4j Scala repo set up independently from the
>> main Log4j repo (and doing Log4j Boot on the side; this will be released
>> independently, so don't worry about this blocking anything) and doing some
>> general site cleanups and whatnot. For 2.8, the other non-core modules will
>> most likely remain where they are and the Log4j Scala API repo gets to be
>> our first foray into the separated repos space.
>>
>> Feature-wise, are there any other things we'd like to complete before
>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>> pain points of migrating config formats being brought up again, so it would
>> be great to get our Log4j 1 config support in this release,
>>
>
> There is already some support for the Log4j1 properties format. Nothing
> for XML IIRC though.
>
> Gary
>
> but that depends on timing, too (we could always RERO and add it to the
>> next release if nobody has time to finish that feature).
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
>
> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
> JUnit in Action, Second Edition
> <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
>
> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
> Spring Batch in Action
> <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Remaining tasks for a 2.8 release
Posted by Remko Popma <re...@gmail.com>.
I would like to do more on the Log4j 1 support but have been swamped at work. Should not be a showstopper for 2.8 though.
Sent from my iPhone
> On Jan 18, 2017, at 4:11, Gary Gregory <ga...@gmail.com> wrote:
>
>> On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <bo...@gmail.com> wrote:
>> I'm working on getting the Log4j Scala repo set up independently from the main Log4j repo (and doing Log4j Boot on the side; this will be released independently, so don't worry about this blocking anything) and doing some general site cleanups and whatnot. For 2.8, the other non-core modules will most likely remain where they are and the Log4j Scala API repo gets to be our first foray into the separated repos space.
>>
>> Feature-wise, are there any other things we'd like to complete before cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the pain points of migrating config formats being brought up again, so it would be great to get our Log4j 1 config support in this release,
>
> There is already some support for the Log4j1 properties format. Nothing for XML IIRC though.
>
> Gary
>
>> but that depends on timing, too (we could always RERO and add it to the next release if nobody has time to finish that feature).
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@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: Remaining tasks for a 2.8 release
Posted by Matt Sicker <bo...@gmail.com>.
Ralph, you can add yourself as a reviewer on GitHub by commenting on a line
in the diff. It should offer you the ability to start a review then.
On 18 January 2017 at 08:17, Apache <ra...@dslextreme.com> wrote:
> That will probably cover 80% of the use cases. Another option is to use a
> proxy factory that reads the file and determines if logger.rootLogger or
> logger.appender is present and routes to the Log4j1ConfigurationFactory if
> it is and the Log4j2 factory if it is not.
>
> Ralph
>
> On Jan 18, 2017, at 6:24 AM, Remko Popma <re...@gmail.com> wrote:
>
> FYI, it seems to me that if Log4j1ConfigurationFactory has SUFFIXES = {
> "log4j.properties"}, then it would not clash with log4j2.properties file
> but could still work as one of the automatic configuration factories.
>
> On Wed, Jan 18, 2017 at 9:51 PM, Mikael Ståldal <mikael.staldal@magine.com
> > wrote:
>
>> I think that Log4j1ConfigurationConverter does not handle Log4j 1.x
>> property substitution correctly. Log4j 1.x let you override properties with
>> Java System Properties, but Log4j 2.x only do that when you specify
>> ${sys:key}. Right?
>>
>> So the converter needs to convert from ${key} to ${sys:key}, and also
>> have some logic to handle the case of default value when present.
>>
>> On Tue, Jan 17, 2017 at 8:11 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>
>>> On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>>> I'm working on getting the Log4j Scala repo set up independently from
>>>> the main Log4j repo (and doing Log4j Boot on the side; this will be
>>>> released independently, so don't worry about this blocking anything) and
>>>> doing some general site cleanups and whatnot. For 2.8, the other non-core
>>>> modules will most likely remain where they are and the Log4j Scala API repo
>>>> gets to be our first foray into the separated repos space.
>>>>
>>>> Feature-wise, are there any other things we'd like to complete before
>>>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>>>> pain points of migrating config formats being brought up again, so it would
>>>> be great to get our Log4j 1 config support in this release,
>>>>
>>>
>>> There is already some support for the Log4j1 properties format. Nothing
>>> for XML IIRC though.
>>>
>>> Gary
>>>
>>> but that depends on timing, too (we could always RERO and add it to the
>>>> next release if nobody has time to finish that feature).
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>>
>>>
>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
>>>
>>> <http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
>>> JUnit in Action, Second Edition
>>> <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
>>>
>>> <http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
>>> Spring Batch in Action
>>> <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>>> <http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> [image: MagineTV]
>>
>> *Mikael Ståldal*
>> Senior software developer
>>
>> *Magine TV*
>> mikael.staldal@magine.com
>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>
>> Privileged and/or Confidential Information may be contained in this
>> message. If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may
>> not copy or deliver this message to anyone. In such case,
>> you should destroy this message and kindly notify the sender by reply
>> email.
>>
>
>
>
--
Matt Sicker <bo...@gmail.com>
Re: Remaining tasks for a 2.8 release
Posted by Apache <ra...@dslextreme.com>.
That will probably cover 80% of the use cases. Another option is to use a proxy factory that reads the file and determines if logger.rootLogger or logger.appender is present and routes to the Log4j1ConfigurationFactory if it is and the Log4j2 factory if it is not.
Ralph
> On Jan 18, 2017, at 6:24 AM, Remko Popma <re...@gmail.com> wrote:
>
> FYI, it seems to me that if Log4j1ConfigurationFactory has SUFFIXES = {"log4j.properties"}, then it would not clash with log4j2.properties file but could still work as one of the automatic configuration factories.
>
> On Wed, Jan 18, 2017 at 9:51 PM, Mikael Ståldal <mikael.staldal@magine.com <ma...@magine.com>> wrote:
> I think that Log4j1ConfigurationConverter does not handle Log4j 1.x property substitution correctly. Log4j 1.x let you override properties with Java System Properties, but Log4j 2.x only do that when you specify ${sys:key}. Right?
>
> So the converter needs to convert from ${key} to ${sys:key}, and also have some logic to handle the case of default value when present.
>
> On Tue, Jan 17, 2017 at 8:11 PM, Gary Gregory <garydgregory@gmail.com <ma...@gmail.com>> wrote:
> On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <boards@gmail.com <ma...@gmail.com>> wrote:
> I'm working on getting the Log4j Scala repo set up independently from the main Log4j repo (and doing Log4j Boot on the side; this will be released independently, so don't worry about this blocking anything) and doing some general site cleanups and whatnot. For 2.8, the other non-core modules will most likely remain where they are and the Log4j Scala API repo gets to be our first foray into the separated repos space.
>
> Feature-wise, are there any other things we'd like to complete before cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the pain points of migrating config formats being brought up again, so it would be great to get our Log4j 1 config support in this release,
>
> There is already some support for the Log4j1 properties format. Nothing for XML IIRC though.
>
> Gary
>
> but that depends on timing, too (we could always RERO and add it to the next release if nobody has time to finish that feature).
>
> --
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com <ma...@gmail.com> | ggregory@apache.org <ma...@apache.org>
> Java Persistence with Hibernate, Second Edition <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8> <http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
> JUnit in Action, Second Edition <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22> <http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
> Spring Batch in Action <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action> <http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/>
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
>
>
> --
>
>
> Mikael Ståldal
> Senior software developer
>
> Magine TV
> mikael.staldal@magine.com <ma...@magine.com>
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com <http://www.magine.com/>
>
> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply email.
>
Re: Remaining tasks for a 2.8 release
Posted by Remko Popma <re...@gmail.com>.
FYI, it seems to me that if Log4j1ConfigurationFactory has SUFFIXES = {
"log4j.properties"}, then it would not clash with log4j2.properties file
but could still work as one of the automatic configuration factories.
On Wed, Jan 18, 2017 at 9:51 PM, Mikael Ståldal <mi...@magine.com>
wrote:
> I think that Log4j1ConfigurationConverter does not handle Log4j 1.x
> property substitution correctly. Log4j 1.x let you override properties with
> Java System Properties, but Log4j 2.x only do that when you specify
> ${sys:key}. Right?
>
> So the converter needs to convert from ${key} to ${sys:key}, and also have
> some logic to handle the case of default value when present.
>
> On Tue, Jan 17, 2017 at 8:11 PM, Gary Gregory <ga...@gmail.com>
> wrote:
>
>> On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>>> I'm working on getting the Log4j Scala repo set up independently from
>>> the main Log4j repo (and doing Log4j Boot on the side; this will be
>>> released independently, so don't worry about this blocking anything) and
>>> doing some general site cleanups and whatnot. For 2.8, the other non-core
>>> modules will most likely remain where they are and the Log4j Scala API repo
>>> gets to be our first foray into the separated repos space.
>>>
>>> Feature-wise, are there any other things we'd like to complete before
>>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>>> pain points of migrating config formats being brought up again, so it would
>>> be great to get our Log4j 1 config support in this release,
>>>
>>
>> There is already some support for the Log4j1 properties format. Nothing
>> for XML IIRC though.
>>
>> Gary
>>
>> but that depends on timing, too (we could always RERO and add it to the
>>> next release if nobody has time to finish that feature).
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
>>
>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
>> JUnit in Action, Second Edition
>> <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
>>
>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
>> Spring Batch in Action
>> <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
JIRA issue for Log4j 1.x property substitution:
https://issues.apache.org/jira/browse/LOG4J2-1792
On Wed, Jan 18, 2017 at 1:51 PM, Mikael Ståldal <mi...@magine.com>
wrote:
> I think that Log4j1ConfigurationConverter does not handle Log4j 1.x
> property substitution correctly. Log4j 1.x let you override properties with
> Java System Properties, but Log4j 2.x only do that when you specify
> ${sys:key}. Right?
>
> So the converter needs to convert from ${key} to ${sys:key}, and also have
> some logic to handle the case of default value when present.
>
> On Tue, Jan 17, 2017 at 8:11 PM, Gary Gregory <ga...@gmail.com>
> wrote:
>
>> On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>>> I'm working on getting the Log4j Scala repo set up independently from
>>> the main Log4j repo (and doing Log4j Boot on the side; this will be
>>> released independently, so don't worry about this blocking anything) and
>>> doing some general site cleanups and whatnot. For 2.8, the other non-core
>>> modules will most likely remain where they are and the Log4j Scala API repo
>>> gets to be our first foray into the separated repos space.
>>>
>>> Feature-wise, are there any other things we'd like to complete before
>>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>>> pain points of migrating config formats being brought up again, so it would
>>> be great to get our Log4j 1 config support in this release,
>>>
>>
>> There is already some support for the Log4j1 properties format. Nothing
>> for XML IIRC though.
>>
>> Gary
>>
>> but that depends on timing, too (we could always RERO and add it to the
>>> next release if nobody has time to finish that feature).
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
>>
>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
>> JUnit in Action, Second Edition
>> <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
>>
>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
>> Spring Batch in Action
>> <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
I think that Log4j1ConfigurationConverter does not handle Log4j 1.x
property substitution correctly. Log4j 1.x let you override properties with
Java System Properties, but Log4j 2.x only do that when you specify
${sys:key}. Right?
So the converter needs to convert from ${key} to ${sys:key}, and also have
some logic to handle the case of default value when present.
On Tue, Jan 17, 2017 at 8:11 PM, Gary Gregory <ga...@gmail.com>
wrote:
> On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <bo...@gmail.com> wrote:
>
>> I'm working on getting the Log4j Scala repo set up independently from the
>> main Log4j repo (and doing Log4j Boot on the side; this will be released
>> independently, so don't worry about this blocking anything) and doing some
>> general site cleanups and whatnot. For 2.8, the other non-core modules will
>> most likely remain where they are and the Log4j Scala API repo gets to be
>> our first foray into the separated repos space.
>>
>> Feature-wise, are there any other things we'd like to complete before
>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>> pain points of migrating config formats being brought up again, so it would
>> be great to get our Log4j 1 config support in this release,
>>
>
> There is already some support for the Log4j1 properties format. Nothing
> for XML IIRC though.
>
> Gary
>
> but that depends on timing, too (we could always RERO and add it to the
>> next release if nobody has time to finish that feature).
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
>
> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
> JUnit in Action, Second Edition
> <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
>
> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
> Spring Batch in Action
> <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Remaining tasks for a 2.8 release
Posted by Gary Gregory <ga...@gmail.com>.
On Tue, Jan 17, 2017 at 8:04 AM, Matt Sicker <bo...@gmail.com> wrote:
> I'm working on getting the Log4j Scala repo set up independently from the
> main Log4j repo (and doing Log4j Boot on the side; this will be released
> independently, so don't worry about this blocking anything) and doing some
> general site cleanups and whatnot. For 2.8, the other non-core modules will
> most likely remain where they are and the Log4j Scala API repo gets to be
> our first foray into the separated repos space.
>
> Feature-wise, are there any other things we'd like to complete before
> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
> pain points of migrating config formats being brought up again, so it would
> be great to get our Log4j 1 config support in this release,
>
There is already some support for the Log4j1 properties format. Nothing for
XML IIRC though.
Gary
but that depends on timing, too (we could always RERO and add it to the
> next release if nobody has time to finish that feature).
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Remaining tasks for a 2.8 release
Posted by Remko Popma <re...@gmail.com>.
About LOG4J2-1648, let's keep it open for now. Not sure if the extension point has been documented.
Sent from my iPhone
> On Jan 18, 2017, at 1:43, Mikael Ståldal <mi...@magine.com> wrote:
>
> And what about LOG4J2-1648 ?
>
> Is that done, or is there anything left to do?
>
>> On Tue, Jan 17, 2017 at 5:20 PM, Mikael Ståldal <mi...@magine.com> wrote:
>> I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I have a branch out for review.
>>
>>
>>> On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <bo...@gmail.com> wrote:
>>> I'm working on getting the Log4j Scala repo set up independently from the main Log4j repo (and doing Log4j Boot on the side; this will be released independently, so don't worry about this blocking anything) and doing some general site cleanups and whatnot. For 2.8, the other non-core modules will most likely remain where they are and the Log4j Scala API repo gets to be our first foray into the separated repos space.
>>>
>>> Feature-wise, are there any other things we'd like to complete before cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the pain points of migrating config formats being brought up again, so it would be great to get our Log4j 1 config support in this release, but that depends on timing, too (we could always RERO and add it to the next release if nobody has time to finish that feature).
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>> --
>>
>>
>> Mikael Ståldal
>> Senior software developer
>>
>> Magine TV
>> mikael.staldal@magine.com
>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>
>> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
>> you should destroy this message and kindly notify the sender by reply email.
>
>
>
> --
>
>
> Mikael Ståldal
> Senior software developer
>
> Magine TV
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply email.
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
And what about LOG4J2-1648
<https://issues.apache.org/jira/browse/LOG4J2-1648> ?
Is that done, or is there anything left to do?
On Tue, Jan 17, 2017 at 5:20 PM, Mikael Ståldal <mi...@magine.com>
wrote:
> I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I
> have a branch out for review.
>
>
> On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <bo...@gmail.com> wrote:
>
>> I'm working on getting the Log4j Scala repo set up independently from the
>> main Log4j repo (and doing Log4j Boot on the side; this will be released
>> independently, so don't worry about this blocking anything) and doing some
>> general site cleanups and whatnot. For 2.8, the other non-core modules will
>> most likely remain where they are and the Log4j Scala API repo gets to be
>> our first foray into the separated repos space.
>>
>> Feature-wise, are there any other things we'd like to complete before
>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>> pain points of migrating config formats being brought up again, so it would
>> be great to get our Log4j 1 config support in this release, but that
>> depends on timing, too (we could always RERO and add it to the next release
>> if nobody has time to finish that feature).
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
What is left to do on LOG4J2-1648
<https://issues.apache.org/jira/browse/LOG4J2-1648> ? Only documentation?
On Wed, Jan 18, 2017 at 2:10 AM, Apache <ra...@dslextreme.com> wrote:
> How do I add myself as a reviewer?
>
> Ralph
>
> On Jan 17, 2017, at 2:05 PM, Mikael Ståldal <mi...@magine.com>
> wrote:
>
> OK, Pull Request here:
>
> https://github.com/apache/logging-log4j2/pull/55
>
> On Jan 17, 2017 6:58 PM, "Matt Sicker" <bo...@gmail.com> wrote:
>
>> Are you able to make a PR on GitHub for review? That'd be a neat way to
>> interactively review our own internal branches. Not sure if you need to do
>> it from a fork, though.
>>
>> On 17 January 2017 at 10:20, Mikael Ståldal <mi...@magine.com>
>> wrote:
>>
>>> I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I
>>> have a branch out for review.
>>>
>>>
>>> On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>>> I'm working on getting the Log4j Scala repo set up independently from
>>>> the main Log4j repo (and doing Log4j Boot on the side; this will be
>>>> released independently, so don't worry about this blocking anything) and
>>>> doing some general site cleanups and whatnot. For 2.8, the other non-core
>>>> modules will most likely remain where they are and the Log4j Scala API repo
>>>> gets to be our first foray into the separated repos space.
>>>>
>>>> Feature-wise, are there any other things we'd like to complete before
>>>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>>>> pain points of migrating config formats being brought up again, so it would
>>>> be great to get our Log4j 1 config support in this release, but that
>>>> depends on timing, too (we could always RERO and add it to the next release
>>>> if nobody has time to finish that feature).
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>>
>>>
>>>
>>>
>>> --
>>> [image: MagineTV]
>>>
>>> *Mikael Ståldal*
>>> Senior software developer
>>>
>>> *Magine TV*
>>> mikael.staldal@magine.com
>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>>
>>> Privileged and/or Confidential Information may be contained in this
>>> message. If you are not the addressee indicated in this message
>>> (or responsible for delivery of the message to such a person), you may
>>> not copy or deliver this message to anyone. In such case,
>>> you should destroy this message and kindly notify the sender by reply
>>> email.
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
Maybe Matt can describe how he got added as reviewer? I cannot test it
myself since GitHub forbids review of your own PR:s.
On Wed, Jan 18, 2017 at 2:10 AM, Apache <ra...@dslextreme.com> wrote:
> How do I add myself as a reviewer?
>
> Ralph
>
> On Jan 17, 2017, at 2:05 PM, Mikael Ståldal <mi...@magine.com>
> wrote:
>
> OK, Pull Request here:
>
> https://github.com/apache/logging-log4j2/pull/55
>
> On Jan 17, 2017 6:58 PM, "Matt Sicker" <bo...@gmail.com> wrote:
>
>> Are you able to make a PR on GitHub for review? That'd be a neat way to
>> interactively review our own internal branches. Not sure if you need to do
>> it from a fork, though.
>>
>> On 17 January 2017 at 10:20, Mikael Ståldal <mi...@magine.com>
>> wrote:
>>
>>> I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I
>>> have a branch out for review.
>>>
>>>
>>> On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>>> I'm working on getting the Log4j Scala repo set up independently from
>>>> the main Log4j repo (and doing Log4j Boot on the side; this will be
>>>> released independently, so don't worry about this blocking anything) and
>>>> doing some general site cleanups and whatnot. For 2.8, the other non-core
>>>> modules will most likely remain where they are and the Log4j Scala API repo
>>>> gets to be our first foray into the separated repos space.
>>>>
>>>> Feature-wise, are there any other things we'd like to complete before
>>>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>>>> pain points of migrating config formats being brought up again, so it would
>>>> be great to get our Log4j 1 config support in this release, but that
>>>> depends on timing, too (we could always RERO and add it to the next release
>>>> if nobody has time to finish that feature).
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>>
>>>
>>>
>>>
>>> --
>>> [image: MagineTV]
>>>
>>> *Mikael Ståldal*
>>> Senior software developer
>>>
>>> *Magine TV*
>>> mikael.staldal@magine.com
>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>>
>>> Privileged and/or Confidential Information may be contained in this
>>> message. If you are not the addressee indicated in this message
>>> (or responsible for delivery of the message to such a person), you may
>>> not copy or deliver this message to anyone. In such case,
>>> you should destroy this message and kindly notify the sender by reply
>>> email.
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Remaining tasks for a 2.8 release
Posted by Apache <ra...@dslextreme.com>.
How do I add myself as a reviewer?
Ralph
> On Jan 17, 2017, at 2:05 PM, Mikael Ståldal <mi...@magine.com> wrote:
>
> OK, Pull Request here:
>
> https://github.com/apache/logging-log4j2/pull/55 <https://github.com/apache/logging-log4j2/pull/55>
>
> On Jan 17, 2017 6:58 PM, "Matt Sicker" <boards@gmail.com <ma...@gmail.com>> wrote:
> Are you able to make a PR on GitHub for review? That'd be a neat way to interactively review our own internal branches. Not sure if you need to do it from a fork, though.
>
> On 17 January 2017 at 10:20, Mikael Ståldal <mikael.staldal@magine.com <ma...@magine.com>> wrote:
> I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I have a branch out for review.
>
>
> On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <boards@gmail.com <ma...@gmail.com>> wrote:
> I'm working on getting the Log4j Scala repo set up independently from the main Log4j repo (and doing Log4j Boot on the side; this will be released independently, so don't worry about this blocking anything) and doing some general site cleanups and whatnot. For 2.8, the other non-core modules will most likely remain where they are and the Log4j Scala API repo gets to be our first foray into the separated repos space.
>
> Feature-wise, are there any other things we'd like to complete before cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the pain points of migrating config formats being brought up again, so it would be great to get our Log4j 1 config support in this release, but that depends on timing, too (we could always RERO and add it to the next release if nobody has time to finish that feature).
>
> --
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
>
>
>
> --
>
>
> Mikael Ståldal
> Senior software developer
>
> Magine TV
> mikael.staldal@magine.com <ma...@magine.com>
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com <http://www.magine.com/>
>
> Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply email.
>
>
>
> --
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
OK, Pull Request here:
https://github.com/apache/logging-log4j2/pull/55
On Jan 17, 2017 6:58 PM, "Matt Sicker" <bo...@gmail.com> wrote:
> Are you able to make a PR on GitHub for review? That'd be a neat way to
> interactively review our own internal branches. Not sure if you need to do
> it from a fork, though.
>
> On 17 January 2017 at 10:20, Mikael Ståldal <mi...@magine.com>
> wrote:
>
>> I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I
>> have a branch out for review.
>>
>>
>> On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <bo...@gmail.com> wrote:
>>
>>> I'm working on getting the Log4j Scala repo set up independently from
>>> the main Log4j repo (and doing Log4j Boot on the side; this will be
>>> released independently, so don't worry about this blocking anything) and
>>> doing some general site cleanups and whatnot. For 2.8, the other non-core
>>> modules will most likely remain where they are and the Log4j Scala API repo
>>> gets to be our first foray into the separated repos space.
>>>
>>> Feature-wise, are there any other things we'd like to complete before
>>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>>> pain points of migrating config formats being brought up again, so it would
>>> be great to get our Log4j 1 config support in this release, but that
>>> depends on timing, too (we could always RERO and add it to the next release
>>> if nobody has time to finish that feature).
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>> --
>> [image: MagineTV]
>>
>> *Mikael Ståldal*
>> Senior software developer
>>
>> *Magine TV*
>> mikael.staldal@magine.com
>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>>
>> Privileged and/or Confidential Information may be contained in this
>> message. If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may
>> not copy or deliver this message to anyone. In such case,
>> you should destroy this message and kindly notify the sender by reply
>> email.
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: Remaining tasks for a 2.8 release
Posted by Matt Sicker <bo...@gmail.com>.
Are you able to make a PR on GitHub for review? That'd be a neat way to
interactively review our own internal branches. Not sure if you need to do
it from a fork, though.
On 17 January 2017 at 10:20, Mikael Ståldal <mi...@magine.com>
wrote:
> I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I
> have a branch out for review.
>
>
> On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <bo...@gmail.com> wrote:
>
>> I'm working on getting the Log4j Scala repo set up independently from the
>> main Log4j repo (and doing Log4j Boot on the side; this will be released
>> independently, so don't worry about this blocking anything) and doing some
>> general site cleanups and whatnot. For 2.8, the other non-core modules will
>> most likely remain where they are and the Log4j Scala API repo gets to be
>> our first foray into the separated repos space.
>>
>> Feature-wise, are there any other things we'd like to complete before
>> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
>> pain points of migrating config formats being brought up again, so it would
>> be great to get our Log4j 1 config support in this release, but that
>> depends on timing, too (we could always RERO and add it to the next release
>> if nobody has time to finish that feature).
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>
--
Matt Sicker <bo...@gmail.com>
Re: Remaining tasks for a 2.8 release
Posted by Mikael Ståldal <mi...@magine.com>.
I think we should get LOG4J2-1748 and LOG4J2-1780 resolved before 2.8, I
have a branch out for review.
On Tue, Jan 17, 2017 at 5:04 PM, Matt Sicker <bo...@gmail.com> wrote:
> I'm working on getting the Log4j Scala repo set up independently from the
> main Log4j repo (and doing Log4j Boot on the side; this will be released
> independently, so don't worry about this blocking anything) and doing some
> general site cleanups and whatnot. For 2.8, the other non-core modules will
> most likely remain where they are and the Log4j Scala API repo gets to be
> our first foray into the separated repos space.
>
> Feature-wise, are there any other things we'd like to complete before
> cutting a 2.8 release? Based on the ongoing Zookeeper migration, I see the
> pain points of migrating config formats being brought up again, so it would
> be great to get our Log4j 1 config support in this release, but that
> depends on timing, too (we could always RERO and add it to the next release
> if nobody has time to finish that feature).
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.