No; I simply called it "logging.properties". But I am certain that the
file was read and used as a properties file (that was easy to figure out).
Karl
On Mon, Apr 17, 2017 at 6:13 AM, Furkan KAMACI
wrote:
> Hi Karl,
>
> Just to double check: did you named properties
Hi Karl,
Just to double check: did you named properties file as log4j2.properties?
Kind Regards,
Furkan KAMACI
On Mon, Apr 17, 2017 at 12:48 PM, Karl Wright wrote:
> FWIW, it turns out that I could not get a .properties configuration to
> work. But I was able to get an
FWIW, it turns out that I could not get a .properties configuration to
work. But I was able to get an XML configuration to work, so I switched to
that.
Karl
On Sun, Apr 16, 2017 at 8:45 AM, Karl Wright wrote:
> Yes, of course.
> Karl
>
> On Apr 16, 2017 8:15 AM, "Furkan
Yes, of course.
Karl
On Apr 16, 2017 8:15 AM, "Furkan KAMACI" wrote:
> Hi Karl,
>
> Did you check here:
> https://logging.apache.org/log4j/2.x/manual/migration.html
>
> Kind Regards,
> Furkan KAMACI
>
> On Sun, Apr 16, 2017 at 9:33 AM, Karl Wright
Hi Karl,
Did you check here:
https://logging.apache.org/log4j/2.x/manual/migration.html
Kind Regards,
Furkan KAMACI
On Sun, Apr 16, 2017 at 9:33 AM, Karl Wright wrote:
> Hi all,
>
> I'm in the process of migrating MCF to log4j 2, but I am having a lot of
> trouble getting
Hi all,
I'm in the process of migrating MCF to log4j 2, but I am having a lot of
trouble getting it to work at all. This is where things stand:
(1) I had to change the name of our logging file from logging.ini to
logging.properties, because otherwise it attempts to interpret it as XML;
(2) The