[
https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011663#comment-16011663
]
Ralph Goers edited comment on LOG4J2-1311 at 5/21/17 5:58 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1311:
Description:
---> Firstly, I'd like to describe some conditions of our environment:
1) Our appl
I hoped to hear that. keeping 4 sln in sync is a major effort with no
profit. Do we want lazy votes when an upgrade to a new vs version is
immanent?
On 21 May 2017 6:02 a.m., "Stefan Bodewig" wrote:
> On 2017-05-19, wrote:
>
> > This migrates the visual studio solution to Visual Studio 14
>
> >
[
https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018689#comment-16018689
]
Girish edited comment on LOG4J2-1311 at 5/21/17 4:28 AM:
-
Any sug
[
https://issues.apache.org/jira/browse/LOG4J2-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018689#comment-16018689
]
Girish commented on LOG4J2-1311:
Any suggestions above issue is appreciated !!!
> Socket
On 2017-05-19, Dominik Psenner wrote:
> would we like to use gitflow for our named branches? [1]
I've used gitflow in one or two projects at work and we've never really
come to a situation where having the release branch really helped. Maybe
because we didn't create bug fix releases on a regular
On 2017-05-19, wrote:
> This migrates the visual studio solution to Visual Studio 14
> --
> src/log4net.vs2012.csproj | 4 ++--
> src/log4net.vs2012.sln| 3 +++
> 2 files changed, 5 insertions(+), 2 deletions(-)
> -
Ralph Goers created LOG4J2-1917:
---
Summary: Log4j api should use Java's ServiceLoader to locate
implememtations
Key: LOG4J2-1917
URL: https://issues.apache.org/jira/browse/LOG4J2-1917
Project: Log4j 2
