Re: [log4j] which branches can be deleted?

2018-02-02 Thread Ralph Goers
Obviously release-2.x needs to stay as you just created it. Master of course has to stay. I’d like to keep android around until we solve that problem. I would have to look at each of the specified Jira issues to know which can be deleted. Ralph > On Feb 2, 2018, at 1:39 AM, Remko Popma wrote:

Re: [log4j] which branches can be deleted?

2018-02-02 Thread Matt Sicker
I removed LOG4J2-1431 as it was merged. You can obviously remove master from that list as well. On 2 February 2018 at 02:39, Remko Popma wrote: > Can some of these branches be deleted? > > >git branch -r --list > origin/2.0-beta1 > origin/AutoCloseableLock > origin/GenericMapMessage > or

Re: Extend daily log file appender

2018-02-02 Thread Remko Popma
Take a look at the RewriteAppender (https://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender). That may be a good start. Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Feb 2, 2018, at 21:48, Walter Heestermans (TME) > wrote: > > I take a

RE: Extend daily log file appender

2018-02-02 Thread Walter Heestermans (TME)
I take a look in that direction, true that the appender logic is not to be amended, only the text to be logged, so converter should be enough. Regards Walter -Original Message- From: Chandra [mailto:chandra.tungathur...@rwth-aachen.de] Sent: 02 February 2018 13:44 To: dev@logging.apache.

RE: Extend daily log file appender

2018-02-02 Thread Chandra
I believe custom pattern converter should suffice in your case. You could create a converter which encrypts the log event data. Reg, Chandra On 2 Feb 2018, 5:53 PM +0530, Walter Heestermans (TME) , wrote: > We like to do the encryption outside the application logging,a nd centralized > inside

RE: Extend daily log file appender

2018-02-02 Thread Walter Heestermans (TME)
We like to do the encryption outside the application logging,a nd centralized inside the logger Regards, Walter -Original Message- From: Chandra [mailto:chandra.tungathur...@rwth-aachen.de] Sent: 02 February 2018 12:30 To: dev@logging.apache.org; dev@logging.apache.org Subject: Re: Exte

Antwort: [Newsletter] Extend daily log file appender

2018-02-02 Thread Jonas . Baehr
Hi, Which log4 are you using? For log4net you can implement a LockingModel [1] for the (rolling) file appender that wraps the aquired stream. This works quite nicely for compression (wrap the underlaying file stream in a gzip stream [2]) or encryption (wrap in crypto stream [3]). Just ensure t

Re: Extend daily log file appender

2018-02-02 Thread Chandra
any issues to log encrypted data directly? Reg, Chandra On 2 Feb 2018, 4:31 PM +0530, Walter Heestermans (TME) , wrote: > Hi, > > For GDPR we should have some log4 log appender (extended from daily log file > appender) that encrypts the log information. > > Anybody aware of some appender doing

Extend daily log file appender

2018-02-02 Thread Walter Heestermans (TME)
Hi, For GDPR we should have some log4 log appender (extended from daily log file appender) that encrypts the log information. Anybody aware of some appender doing that? If not can somebody provide sample to create own appender based on the default daily file logger? Regards Walter This e-ma

[log4j] which branches can be deleted?

2018-02-02 Thread Remko Popma
Can some of these branches be deleted? >git branch -r --list origin/2.0-beta1 origin/AutoCloseableLock origin/GenericMapMessage origin/GenericMapMessageSimple origin/LOG4J2-1116 (Web app-friendly thread locals for gc-free logging (was: upgrade to log4j2 causes too frequent minor gc)) o