Thanks, great.
On Wed, Jun 15, 2016 at 3:05 PM, Vanya Seth wrote:
> Hi Lars
>
> We will make that change.
>
> Regards
> Vanya
>
> On Wed, Jun 15, 2016 at 2:37 PM, Lars Helge Øverland
> wrote:
>
>>
>> Hi Vanya,
>>
>> I understand your concerns here.
>>
>> However this is fine with me - this logg
Hi Lars
We will make that change.
Regards
Vanya
On Wed, Jun 15, 2016 at 2:37 PM, Lars Helge Øverland wrote:
>
> Hi Vanya,
>
> I understand your concerns here.
>
> However this is fine with me - this logging is not visible to users and
> there won't even be produced a log file if the sync isn't
Hi Vanya,
I understand your concerns here.
However this is fine with me - this logging is not visible to users and
there won't even be produced a log file if the sync isn't enabled, so I'm
fine with you adding a new logger to Log4JLogConfigInitializer. Let me know
what you think.
best regards,
Hi Lars
The metadata versioning and sync is an optional feature. It totally depends
on the deployment strategy that we want to adopt and given that whether we
choose to do metadata sync or not.
For these reasons adding the metadata sync log as a first class citizen to
the Log4JLogConfigInitialize
Hi there,
okay. It would be great if we do not introduce another way of doing
logging. The problem is that resolving the DHIS2_HOME directory is a bit
complex - the system looks for the system property dhis2.home, the env
variable DHIS2_HOME, then falls back to opt/dhis2. log4j 1 does not support
Hi Lars,
We are using log4j.properties file instead of 'Log4JLogConfigInitializer'
for metadata sync logging purpose. The FILE parameter of FileAppender in
log4j.properties needs the value of DHIS2_HOME environment variable to save
the metadata sync log in the same folder location as that of the o
6 matches
Mail list logo
