On Sun, Jun 4, 2017 at 3:34 PM, Matt Sicker wrote:
> Raw type warnings? In my experience, barely anyone even notices them let
> alone fixes them. :/
>
Right, warnings like (if you have them turned on, I do in Eclipse):
"MapMessage is a raw type. References to generic type MapMessage
should be p
Raw type warnings? In my experience, barely anyone even notices them let
alone fixes them. :/
On 4 June 2017 at 16:57, Ralph Goers wrote:
> It is reasonable but I really dislike having to tell users they need to
> change their code to get rid of the new warnings.
>
> Ralph
>
> > On Jun 4, 2017,
It is reasonable but I really dislike having to tell users they need to change
their code to get rid of the new warnings.
Ralph
> On Jun 4, 2017, at 9:48 AM, Gary Gregory wrote:
>
> Hi,
>
> I was about to merger the branch GenericMapMessageSimple when I realized
> something... Right now, all
Sounds pretty reasonable to me.
On 4 June 2017 at 11:48, Gary Gregory wrote:
> Hi,
>
> I was about to merger the branch GenericMapMessageSimple when I realized
> something... Right now, all the code compiles and runs cleanly and the
> Clirr check passes.
>
> But...
>
> Because of the new impleme
Hi,
I was about to merger the branch GenericMapMessageSimple when I realized
something... Right now, all the code compiles and runs cleanly and the
Clirr check passes.
But...
Because of the new implementation declares MapMessage with generics, we do
get compiler warnings about MapMessage not bei
Github user imriz commented on the issue:
https://github.com/apache/logging-log4j2/pull/81
@mikaelstaldal Hi :) I've extended this to YAML and XML + updated
`layouts.xml.vm`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Roman Sosnin created LOG4J2-1933:
Summary: Not able to init config with JsonConfiguration class
while the json config nodes are in random order
Key: LOG4J2-1933
URL: https://issues.apache.org/jira/browse/LOG4J2-19
