[jira] [Commented] (LOGCXX-483) Not able to see hebrew values when logging in log4cxx

[ https://issues.apache.org/jira/browse/LOGCXX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045365#comment-16045365 ] Matt Sicker commented on LOGCXX-483: I'm not sure how appropriate it is for a library

[jira] [Comment Edited] (LOGCXX-483) Not able to see hebrew values when logging in log4cxx

[ https://issues.apache.org/jira/browse/LOGCXX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045332#comment-16045332 ] Robert Middleton edited comment on LOGCXX-483 at 6/10/17 2:57 AM: --

[jira] [Commented] (LOGCXX-483) Not able to see hebrew values when logging in log4cxx

[ https://issues.apache.org/jira/browse/LOGCXX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045332#comment-16045332 ] Robert Middleton commented on LOGCXX-483: - I just looked at this a little more jus

Re: LOGCXX Jira Mail Setting

Yeah, it's a simple infra request, though now that we've been using it for a couple months, I'm starting to wonder how useful it is. It makes JIRA itself have some useful info integrated, but all these separate sources of notifications do not work well together apparently. On 9 June 2017 at 19:16,

[GitHub] logging-log4cxx pull request #2: Build with autotools+maven

GitHub user rm5248 opened a pull request: https://github.com/apache/logging-log4cxx/pull/2 Build with autotools+maven This fix updates the log4cxx maven file to build with Maven properly when running on Linux. It is rather simplistic at this point, and it will break on Wind

Re: LOGCXX Jira Mail Setting

Related note: I see that commits to log4j2 that have a comment from the ASF subversion/git bot when somethings gets committed, does that also have to be setup? It's not doing it for log4cxx. I find that those e-mails are a little annoying, but I do like having the commits with the issues in JIRA(

Re: [LOG4NET] [VOTE] gitflow

Agreed. Whenever I've used git-flow in the past, the only reason we had a develop and master branch was so that it was simpler to write hotfixes against master later on. We'd delete our release branches after they were tagged and merged to master&develop, so the only ways to find what's in producti

Re: [LOG4NET] [VOTE] gitflow

I'm unlikely to do development on Log4jnet but I like having 'master' instead of 'develop' for the reason Julius stated. Gary On Fri, Jun 9, 2017 at 9:07 AM, Julius Davies wrote: > Hi, > > The 'master' branch in the gitflow model is pointless (that state is > already tracked with the 'release/*

[jira] [Commented] (LOGCXX-488) Space after log level hides log messages

[ https://issues.apache.org/jira/browse/LOGCXX-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044694#comment-16044694 ] Sebastian Geiger commented on LOGCXX-488: - Perfect, thanks a lot for fixing this s

Re: [LOG4NET] [VOTE] gitflow

Hi, The 'master' branch in the gitflow model is pointless (that state is already tracked with the 'release/*' branches). I say ditch the 'master' branch and make 'develop' the default branch (e.g., the one that a fresh "git clone" automatically checks out). And rebase the short lived feature br

Re: [LOG4NET] [VOTE] gitflow

Hi, On 2017-05-23 08:49, Stefan Bodewig wrote: Please ensure github tracks develop as the default branch when the vote passes. I just filed an issue on INFRA to make this happen. This is the ticket for it: https://issues.apache.org/jira/browse/INFRA-14316 Cheers, Dominik

Re: [log4net] [jira] [vote] remove "current assignee" from issue notifications

+1 makes sense to me, should help at least somewhat reduce duplicate messages On 9 June 2017 at 10:01, Dominik Psenner wrote: > Hi, > > As a follow up to this discussion I'm starting a vote to remove the > "current assignee" from the list of notifications in the LOG4NET jira > project. This will

Re: Question regarding the Log4j2

This mailing list is for development discussion. You want to try the log4j-user mailing list: https://logging.apache.org/log4j/2.x/mail-lists.html On 8 June 2017 at 17:48, Anhad Singh Bhasin wrote: > Hello, > > I have questions regarding the use of Log4j2 here >

[log4net] [jira] [vote] remove "current assignee" from issue notifications

Hi, As a follow up to this discussion I'm starting a vote to remove the "current assignee" from the list of notifications in the LOG4NET jira project. This will reduce the number of duplicate mails if one has both assigned an issue and is subscribed to the dev list. +1: Yes! -1: No, don't do

[jira] [Resolved] (LOGCXX-488) Space after log level hides log messages

[ https://issues.apache.org/jira/browse/LOGCXX-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-488. -- Resolution: Fixed Fix Version/s: 0.11.0 I've added a test and fixed the problem i

[jira] [Assigned] (LOGCXX-488) Space after log level hides log messages

[ https://issues.apache.org/jira/browse/LOGCXX-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning reassigned LOGCXX-488: Assignee: Thorsten Schöning > Space after log level hides log messages > --

Re: LOGCXX Jira Mail Setting

You may be right, I don't seem to be able to change the "notification scheme" for lig4net either. Stefan On 2017-06-09, Dominik Psenner wrote: > Hi Stefan, > I think this is an administrative task that needs to be done by > INFRA. While I can access the Administration page of the log4net jira >

Re: LOGCXX Jira Mail Setting

Hi Stefan, I think this is an administrative task that needs to be done by INFRA. While I can access the Administration page of the log4net jira project, I can't edit the notifications settings myself. Maybe this applies to logcxx too? {quote url="https://issues.apache.org/jira/plugins/serv

LOGCXX Jira Mail Setting

Hi I just had to moderate through the JIRA mail for LOGCXX-488. It looks as if we needed to fix the address messages for this JIRA project get sent to, but I lack the admin karma to do that myself. Stefan

[jira] [Created] (LOGCXX-488) Space after log level hides log messages

Sebastian Geiger created LOGCXX-488: --- Summary: Space after log level hides log messages Key: LOGCXX-488 URL: https://issues.apache.org/jira/browse/LOGCXX-488 Project: Log4cxx Issue Type: Bu