Just do an import from Eclipse based on Maven projects. Eclipse will pickup
all the POMs and create Eclipse projects on your behalf. Make sure you have
the m2e (Maven to Eclipse) Eclipse plugin. It comes with most Eclipse
distros.
Gary
On Mon, Jan 8, 2018 at 4:53 PM, Clint Weisbrod
wrote:
> Hel
Hello.
I'm hoping to contribute a little to the log4j2 project and was wondering
where I can find documentation on setting up an Eclipse project to make
edits to and debug the source.
I have cloned the git repo and am able to successfully build the project
with Maven, but debugging in Eclipse wou
On Mon, Jan 8, 2018 at 3:49 PM, Remko Popma wrote:
>
>
> > On Jan 9, 2018, at 4:49, ggreg...@apache.org wrote:
> >
> > Repository: logging-log4j2
> > Updated Branches:
> > refs/heads/master 2352052d0 -> 9637dc558
> >
> >
> > [LOG4J2-2177] Replace use of deprecated Core API
> > org.apache.logging
> On Jan 9, 2018, at 4:49, ggreg...@apache.org wrote:
>
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master 2352052d0 -> 9637dc558
>
>
> [LOG4J2-2177] Replace use of deprecated Core API
> org.apache.logging.log4j.core.impl.Log4jLogEvent.Builder.setContextMap(Map String>). Add
Hi,
quite some time passed by since we last made a release and there are a few
issues that have been fixed and should be shipped as part of a release. So
this is my call for help.
There are a few things on the to do list:
- check jira for issues that can be closed as won't fix
- check jira for i
I am on PTO this week. I might find time for this when I am not out having fun
Sent from my iPhone
> On Jan 8, 2018, at 11:24 AM, Mikael Ståldal wrote:
>
> I think that we should at least make a release with fix for
> https://issues.apache.org/jira/browse/LOG4J2-2126 before we try to convince
I think that we should at least make a release with fix for
https://issues.apache.org/jira/browse/LOG4J2-2126 before we try to
convince anyone to use Log4j for something which might be used on Android.
On 2018-01-08 16:37, Gary Gregory wrote:
Hi All:
Over on the d...@hc.apache.org list, we h
Thank you both for replying. It sounds like for now we do not have clean
Android story. I will reply later today to the HC thread with something
like 'We plan on having an Android solution in the future" which means HC
will likely switch to Slf4j for the next alpha/beta. Feel free to comment
over a
On Mon, Jan 8, 2018 at 9:26 AM, Ralph Goers
wrote:
> I have a couple of comments here.
>
> One of the reasons I created Log4j using its own API was due to the
> introduction of Messages. I had discussions on the SLF4J list that made it
> clear that Ceki wasn’t interested in modifying the API to s
I have a couple of comments here.
One of the reasons I created Log4j using its own API was due to the
introduction of Messages. I had discussions on the SLF4J list that made it
clear that Ceki wasn’t interested in modifying the API to support anything more
than Strings. In fact, as a whole SLF4
I've noticed that one of the common complaints when migrating from log4j 1
to 2 (or similar) is the API to modify loggers/appenders/etc. at runtime.
Despite efforts to fulfill the user needs without digging into internals,
it seems like some frameworks or tools prefer convoluted access instead of
m
Hi All:
Over on the d...@hc.apache.org list, we have a thread called "Using SLF4J as
a logging facade; Re: Disagreement on Log4J2" where Oleg (our lead and main
author) has proposed moving from Log4j2 to SLF4J for the next HttpClient
Alpha.
(I had initially switched HC from Commons Logging to Log
12 matches
Mail list logo
