Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #39879

Re: log4j2 test?

Path csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid>
Newsgroups comp.lang.java.programmer
Subject Re: log4j2 test?
Date Tue, 20 Dec 2022 02:17:10 +0100
Organization A noiseless patient Spider
Lines 20
Message-ID <tnr2eo$fum2$1@dont-email.me> (permalink)
References <948bfc5a-7db1-468f-a8de-6f0786c5514fn@googlegroups.com> <tnq49l$crgk$1@dont-email.me> <4b2183f8-8dd9-4f11-a664-85d48a25ce4en@googlegroups.com>
MIME-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
Injection-Date Tue, 20 Dec 2022 01:17:12 -0000 (UTC)
Injection-Info reader01.eternal-september.org; posting-host="dad3a48bd058fdb05e557ce48f28506c"; logging-data="522946"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+hvw5JD+AtSdd7lNrKlDDC"
User-Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0
Cancel-Lock sha1:teiIpZ6OMsmyZVZDqdw92Pzio1g=
Content-Language en-US
In-Reply-To <4b2183f8-8dd9-4f11-a664-85d48a25ce4en@googlegroups.com>
Xref csiph.com comp.lang.java.programmer:39879

Show key headers only | View raw


On 19/12/2022 20:37, e.d.pro...@gmail.com wrote:
> On Monday, December 19, 2022 at 11:42:44 AM UTC-5, Daniele Futtorovic wrote:
>> I would recommend either logging to a fixed place, such as /var/log on a
>> *NIX, or going relative, i.e. against the working directory.
>>
>> Either should fix your problem, as well as make things simpler.
> 
> I ran it with the filename="logs/..." path which should be relative to the build. I haven't looked for the log files from the jenkins build but it didn't crash.
> I was wondering if there was a standard convention for log4j2 writing to files from a maven jenkins build

Something you see more and more these days, especially in containerized 
setups, is straight logging to STDOUT, with the task scheduling layer 
then taking care of digestion/redirection. This is a prime candidate for 
Jenkins builds, which will typically be executed on (often 
containerized) worker slaves, where retrieving files from the filesystem 
at a later date is non-trivial -- whereas consulting the build output, is.

-- 
DF.

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

log4j2 test? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-12-14 06:41 -0800
  Re: log4j2 test? Andreas Leitgeb <avl@logic.at> - 2022-12-16 19:02 +0000
    Re: log4j2 test? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-12-16 12:20 -0800
  Re: log4j2 test? Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid> - 2022-12-19 17:42 +0100
    Re: log4j2 test? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2022-12-19 11:37 -0800
      Re: log4j2 test? Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid> - 2022-12-20 02:17 +0100

csiph-web