Re: Library versions

[Gary Gregory]

Yes, the tool is called "Maven" ;-)

I am also on announce mailing lists of various projects.

Try this:

mvn versions:display-dependency-updates

and:

cls & mvn versions:display-plugin-updates

Gary

On Mon, Nov 13, 2017 at 5:00 PM, Remko Popma  wrote:

> Gary,
>
> Just wondering: how do you keep track of library version updates? Is there
> a tool to get notified when there’s an update?
>
> Amazing job by the way!
>
> Remko
> (Shameless plug) Every java main() method deserves http://picocli.info
>

Library versions

[Remko Popma]

Gary,

Just wondering: how do you keep track of library version updates? Is there
a tool to get notified when there’s an update?

Amazing job by the way!

Remko
(Shameless plug) Every java main() method deserves http://picocli.info

Re: Planning out what we can do to get Chainsaw back in the game

[Ole Ersoy]

Here's a 10 minute video where an Angular timer application is built and 
packaged for all desktops (Apple, M$, Linux - And all browsers) ... in 10 
minutes.

https://www.youtube.com/watch?v=u_vMChpZMCk

If you use the youtube speedup chrome extension you can probably set the 
speedup factor to 2 or 3.  That cuts it down to 3 minutes.

https://chrome.google.com/webstore/detail/youtube-playback-speed-co/hdannnflhlmdablckfkjpleikpphncik?hl=en-US

Love that thing!


On 11/12/2017 11:37 PM, Ralph Goers wrote:

It feels to me that this whole topic has gotten side-tracked.

I think you first need to decide what you want to build before you decide on 
technologies.  Are you building a web application or a desktop? Of course, 
there might be technology that lets you do both, to some degree. As far as I 
know, the only viable language for web applications is Javascript, unless you 
want to build browser plugins. While there might be more variety in desktop 
applications, the usefulness might be more limited - but maybe not. After all, 
there are still a whole lot of desktop based tools around.

But then you have apps like Microsoft Office where they have built a web 
version and a Windows desktop version and a Mac OS desktop version. I have no 
idea how much, if any, of that code is shared, but again, that is an option 
that could be considered.

So again, before going down the rabbit hole of technology discussion, what is 
the scope of what the next version of Chainsaw will be?  Will it be an upgraded 
version of the existing code base that uses something besides Swing, will it be 
something else, or do we want multiple spin-off projects?

Ralph

Re: logging-log4j2 git commit: Fix typo

[Remko Popma]

Sorry, I still see one misspelled Aggreement 

(Away from pc)

> On Nov 14, 2017, at 1:02, rgo...@apache.org wrote:
> 
> Repository: logging-log4j2
> Updated Branches:
>  refs/heads/master ac82a0d78 -> 7ade3025b
> 
> 
> Fix typo
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/7ade3025
> Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/7ade3025
> Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/7ade3025
> 
> Branch: refs/heads/master
> Commit: 7ade3025b8de4176a2149a7aec00362b2380fe61
> Parents: ac82a0d
> Author: Ralph Goers 
> Authored: Mon Nov 13 09:02:30 2017 -0700
> Committer: Ralph Goers 
> Committed: Mon Nov 13 09:02:38 2017 -0700
> 
> --
> README.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> --
> 
> 
> http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/7ade3025/README.md
> --
> diff --git a/README.md b/README.md
> index 36c7f9d..b35cd0e 100644
> --- a/README.md
> +++ b/README.md
> @@ -13,7 +13,7 @@ and provides many of the improvements available in Logback 
> while fixing some inh
> By sending a pull request you grant the Apache Software Foundation sufficient 
> rights to use and release the submitted 
> work under the Apache license. You grant the same rights (copyright license, 
> patent license, etc.) to the 
> Apache Software Foundation as if you have signed a Contributor License 
> Aggreement. For contributions that are 
> -judged to be non-trivial, you will be asked to actually signing a 
> Contributor License Aggreement.
> +judged to be non-trivial, you will be asked to actually signing a 
> Contributor License Agreement.
> 
> ## Usage
> 
> 

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

[Mikael Ståldal]

Nice.

Too bad that Jetty doesn't support automatic discovery of logging impl 
as Tomcat do. Maybe we should issue a feature request about that?



On 2017-11-13 16:49, Gary Gregory wrote:

I also updated log4j-appserver/src/site/markdown/index.md.vm

Thank you!
Gary

On Mon, Nov 13, 2017 at 8:04 AM, Gary Gregory 
wrote:


Oh, I added a section to the main index:

#h3 Integrating with Application Servers

Version 2.10.0 introduces a the module log4j-appserver to improve
integration with Apache Tomcat and Eclipse Jetty.

Gary

On Sun, Nov 12, 2017 at 10:10 AM, Mikael Ståldal  wrote:


On 2017-11-12 16:00, Gary Gregory wrote:


On Sun, Nov 12, 2017 at 7:25 AM, Mikael Ståldal 
wrote:

Do we want a package-info.java in the Jetty package, like in the Tomcat

package?

And you should probably add a section about Jetty integraion in
log4j-appserver/src/site/markdown/index.md.vm



Done. Please review.



I don't see anything about Jetty in log4j-appserver/src/site/markd
own/index.md.vm

Re: [log4j2] org.apache.logging.log4j.appserver.tomcat.TomcatLogger.serialVersionUID

[Ralph Goers]

I copied the file from somewhere else in Log4j and it had it.

Ralph

> On Nov 13, 2017, at 11:00 AM, Gary Gregory  wrote:
> 
> Why does the Tomcat logger
> define org.apache.logging.log4j.appserver.tomcat.TomcatLogger.serialVersionUID
> ?
> 
> Is that class serializable even though it is not declared as a such?
> 
> Thank you,
> Gary

[log4j2] org.apache.logging.log4j.appserver.tomcat.TomcatLogger.serialVersionUID

[Gary Gregory]

Why does the Tomcat logger
define org.apache.logging.log4j.appserver.tomcat.TomcatLogger.serialVersionUID
?

Is that class serializable even though it is not declared as a such?

Thank you,
Gary

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

[Gary Gregory]

In 
org.apache.logging.log4j.appserver.jetty.Log4j2Logger.PrivateManager.getContext():

Is this just a matter of changing false to true in:

public static LoggerContext getContext() {
final ClassLoader cl = Log4j2Logger.class.getClassLoader();
return getContext(FQCN, cl, false);
}

Or is the method supposed to dig up a class loader from a application class
on the stack?

?

Gary

On Mon, Nov 13, 2017 at 9:21 AM, Gary Gregory 
wrote:

> I will take a look...
>
> On Nov 13, 2017 08:43, "Ralph Goers"  wrote:
>
>> Are you planning on fixing this?
>>
>> Ralph
>>
>> > On Nov 11, 2017, at 5:15 PM, Ralph Goers 
>> wrote:
>> >
>> > Because the caller of newLogger(name) is AbstractLogger its ClassLoader
>> will always be used. You need the ClassLoader of the caller of getLogger().
>> >
>> > Ralph
>> >
>> >> On Nov 11, 2017, at 3:43 PM, Gary Gregory 
>> wrote:
>> >>
>> >> Please code review git master. I'm not sure I have the class loader
>> right.
>> >>
>> >> Gary
>> >>
>> >> On Sat, Nov 11, 2017 at 2:54 PM, Ralph Goers <
>> ralph.go...@dslextreme.com>
>> >> wrote:
>> >>
>> >>> Oh, but you probably don’t want to extend AbstractLogger. You really
>> want
>> >>> the FQCN of the caller to be able to identify the ClassLoader and
>> >>> LoggerContext to use and you won’t get that from AbstractLogger’s
>> getLogger
>> >>> method.
>> >>>
>> >>> Ralph
>> >>>
>>  On Nov 11, 2017, at 2:45 PM, Ralph Goers > >
>> >>> wrote:
>> 
>>  Sure. Look at TomcatLogger. It does exactly what you are trying to
>> do.
>> 
>>  Ralph
>> 
>> > On Nov 11, 2017, at 2:02 PM, Gary Gregory 
>> >>> wrote:
>> >
>> > The Javadoc for Log4j's LoggerAdapter says "This registry should
>> not be
>> > used for Log4j Loggers; it is instead used for creating bridges to
>> other
>> > external log systems.".
>> >
>> > In this case we are not bridging TO another log system. We are
>> plugging
>> > INTO Jetty's log system and subclassing Jetty's own LoggerAdapter
>> class
>> > (out convenience.)
>> >
>> > Further thoughts?
>> >
>> > Gary
>> >
>> > On Fri, Nov 10, 2017 at 9:25 PM, Matt Sicker 
>> wrote:
>> >
>> >> IIRC, the easiest way to support it might be to use
>> >> https://logging.apache.org/log4j/2.x/log4j-api/apidocs/
>> >> org/apache/logging/log4j/spi/AbstractLoggerAdapter.html
>> >>
>> >> On 10 November 2017 at 22:16, Gary Gregory > >
>> >>> wrote:
>> >>
>> >>> I think you are correct...
>> >>>
>> >>> Gary
>> >>>
>> >>> On Fri, Nov 10, 2017 at 6:59 PM, Matt Sicker 
>> >>> wrote:
>> >>>
>>  Wouldn't this implementation contain incorrect caller location
>> >>> information?
>> 
>>  On 10 November 2017 at 19:25,  wrote:
>> 
>> > Repository: logging-log4j2
>> > Updated Branches:
>> > refs/heads/master aad2f132b -> 7d52f131e
>> >
>> >
>> > [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse
>> >>> Jetty's
>> > org.eclipse.jetty.util.log.Logger.
>> >
>> > Project: http://git-wip-us.apache.org/r
>> epos/asf/logging-log4j2/repo
>> > Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/
>> > commit/7d52f131
>> > Tree: http://git-wip-us.apache.org/r
>> epos/asf/logging-log4j2/tree/
>>  7d52f131
>> > Diff: http://git-wip-us.apache.org/r
>> epos/asf/logging-log4j2/diff/
>>  7d52f131
>> >
>> > Branch: refs/heads/master
>> > Commit: 7d52f131ec1e000834bcb40343f3f2d41805c75a
>> > Parents: aad2f13
>> > Author: Gary Gregory 
>> > Authored: Fri Nov 10 18:25:47 2017 -0700
>> > Committer: Gary Gregory 
>> > Committed: Fri Nov 10 18:25:47 2017 -0700
>> >
>> > 
>> >> --
>> > log4j-appserver/pom.xml |   8 +
>> > .../log4j/appserver/jetty/Log4j2Logger.java | 184
>>  +++
>> > src/changes/changes.xml |   3 +
>> > 3 files changed, 195 insertions(+)
>> > 
>> >> --
>> >
>> >
>> > http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/
>> > 7d52f131/log4j-appserver/pom.xml
>> > 
>> >> --
>> > diff --git a/log4j-appserver/pom.xml b/log4j-appserver/pom.xml
>> > index e96b1fc..6acd77b 100644
>> 

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

[Gary Gregory]

I will take a look...

On Nov 13, 2017 08:43, "Ralph Goers"  wrote:

> Are you planning on fixing this?
>
> Ralph
>
> > On Nov 11, 2017, at 5:15 PM, Ralph Goers 
> wrote:
> >
> > Because the caller of newLogger(name) is AbstractLogger its ClassLoader
> will always be used. You need the ClassLoader of the caller of getLogger().
> >
> > Ralph
> >
> >> On Nov 11, 2017, at 3:43 PM, Gary Gregory 
> wrote:
> >>
> >> Please code review git master. I'm not sure I have the class loader
> right.
> >>
> >> Gary
> >>
> >> On Sat, Nov 11, 2017 at 2:54 PM, Ralph Goers <
> ralph.go...@dslextreme.com>
> >> wrote:
> >>
> >>> Oh, but you probably don’t want to extend AbstractLogger. You really
> want
> >>> the FQCN of the caller to be able to identify the ClassLoader and
> >>> LoggerContext to use and you won’t get that from AbstractLogger’s
> getLogger
> >>> method.
> >>>
> >>> Ralph
> >>>
>  On Nov 11, 2017, at 2:45 PM, Ralph Goers 
> >>> wrote:
> 
>  Sure. Look at TomcatLogger. It does exactly what you are trying to do.
> 
>  Ralph
> 
> > On Nov 11, 2017, at 2:02 PM, Gary Gregory 
> >>> wrote:
> >
> > The Javadoc for Log4j's LoggerAdapter says "This registry should not
> be
> > used for Log4j Loggers; it is instead used for creating bridges to
> other
> > external log systems.".
> >
> > In this case we are not bridging TO another log system. We are
> plugging
> > INTO Jetty's log system and subclassing Jetty's own LoggerAdapter
> class
> > (out convenience.)
> >
> > Further thoughts?
> >
> > Gary
> >
> > On Fri, Nov 10, 2017 at 9:25 PM, Matt Sicker 
> wrote:
> >
> >> IIRC, the easiest way to support it might be to use
> >> https://logging.apache.org/log4j/2.x/log4j-api/apidocs/
> >> org/apache/logging/log4j/spi/AbstractLoggerAdapter.html
> >>
> >> On 10 November 2017 at 22:16, Gary Gregory 
> >>> wrote:
> >>
> >>> I think you are correct...
> >>>
> >>> Gary
> >>>
> >>> On Fri, Nov 10, 2017 at 6:59 PM, Matt Sicker 
> >>> wrote:
> >>>
>  Wouldn't this implementation contain incorrect caller location
> >>> information?
> 
>  On 10 November 2017 at 19:25,  wrote:
> 
> > Repository: logging-log4j2
> > Updated Branches:
> > refs/heads/master aad2f132b -> 7d52f131e
> >
> >
> > [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse
> >>> Jetty's
> > org.eclipse.jetty.util.log.Logger.
> >
> > Project: http://git-wip-us.apache.org/
> repos/asf/logging-log4j2/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/
> > commit/7d52f131
> > Tree: http://git-wip-us.apache.org/
> repos/asf/logging-log4j2/tree/
>  7d52f131
> > Diff: http://git-wip-us.apache.org/
> repos/asf/logging-log4j2/diff/
>  7d52f131
> >
> > Branch: refs/heads/master
> > Commit: 7d52f131ec1e000834bcb40343f3f2d41805c75a
> > Parents: aad2f13
> > Author: Gary Gregory 
> > Authored: Fri Nov 10 18:25:47 2017 -0700
> > Committer: Gary Gregory 
> > Committed: Fri Nov 10 18:25:47 2017 -0700
> >
> > 
> >> --
> > log4j-appserver/pom.xml |   8 +
> > .../log4j/appserver/jetty/Log4j2Logger.java | 184
>  +++
> > src/changes/changes.xml |   3 +
> > 3 files changed, 195 insertions(+)
> > 
> >> --
> >
> >
> > http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/
> > 7d52f131/log4j-appserver/pom.xml
> > 
> >> --
> > diff --git a/log4j-appserver/pom.xml b/log4j-appserver/pom.xml
> > index e96b1fc..6acd77b 100644
> > --- a/log4j-appserver/pom.xml
> > +++ b/log4j-appserver/pom.xml
> > @@ -34,6 +34,7 @@
> >  Web Documentation
> >  /log4j-appserver
> >  8.5.20
> > +8.2.0.v20160908 
> >  org.apache.logging.log4j.appserver
> > 
> >
> > @@ -56,6 +57,7 @@
> >org.apache.tomcat
> >tomcat-catalina
> >${tomcat.version}
> > +  provided
> >
> >  
> >org.apache.tomcat
> > @@ -71,6 +73,12 @@
> >  
> >
> >  
> > +
> > +  

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

Another thing I noticed is that the downloads page needs to be updated to
link to the (future) dist URLs instead of ones in the site's directory (no
proper mirroring in the old links).

On 12 November 2017 at 19:25, Scott Deboy  wrote:

> I don't recall why - it was a while back :)
>
> Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory
> issue.
>
> On 11/12/17, Matt Sicker  wrote:
> > On 12 November 2017 at 13:53, Scott Deboy  wrote:
> >
> >> That's right -forgot we rev'd to 2.1 internally (info.plist, release
> >> notes, couple other places).
> >>
> >
> > Any particular reason?
> >
> >
> >> Would it be easiest to release the new version as 2.1.0.0 instead of
> >> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
> >> official release with that rev.
> >>
> >
> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's no
> tags
> > or releases for any 2.x release at all, so it seemed like a logical
> > starting point.
> >
> > And thanks for testing! We should be able to clean up for a proper 2.x
> > release. :)
> >
> > --
> > Matt Sicker 
> >
>



-- 
Matt Sicker 

Re: logging-log4j2 git commit: Add PR notice to README

[Remko Popma]

Aggreement-> Agreement
(Away from pc)

On Tue, Nov 14, 2017 at 0:50  wrote:

> Repository: logging-log4j2
> Updated Branches:
>   refs/heads/master d85f39abc -> 8b71dbbf1
>
>
> Add PR notice to README
>
>
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit:
> http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/8b71dbbf
> Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/8b71dbbf
> Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/8b71dbbf
>
> Branch: refs/heads/master
> Commit: 8b71dbbf1038952af4ae23f82817eb875c582ab6
> Parents: d85f39a
> Author: Ralph Goers 
> Authored: Mon Nov 13 08:50:13 2017 -0700
> Committer: Ralph Goers 
> Committed: Mon Nov 13 08:50:27 2017 -0700
>
> --
>  README.md | 8 
>  1 file changed, 8 insertions(+)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/8b71dbbf/README.md
> --
> diff --git a/README.md b/README.md
> index 98d95cf..36c7f9d 100644
> --- a/README.md
> +++ b/README.md
> @@ -7,6 +7,14 @@ and provides many of the improvements available in
> Logback while fixing some inh
>  [![Travis Status](
> https://travis-ci.org/apache/logging-log4j2.svg?branch=master)](https://travis-ci.org/apache/logging-log4j2
> )
>  [![Maven Central](
> https://img.shields.io/maven-central/v/org.apache.logging.log4j/log4j-api.svg)](http://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-api
> )
>
> +
> +## Pull Requests on Github
> +
> +By sending a pull request you grant the Apache Software Foundation
> sufficient rights to use and release the submitted
> +work under the Apache license. You grant the same rights (copyright
> license, patent license, etc.) to the
> +Apache Software Foundation as if you have signed a Contributor License
> Aggreement. For contributions that are
> +judged to be non-trivial, you will be asked to actually signing a
> Contributor License Aggreement.
> +
>  ## Usage
>
>  Users should refer to [Maven, Ivy, Gradle, and SBT Artifacts](
> http://logging.apache.org/log4j/2.x/maven-artifacts.html)
>
>

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

[Gary Gregory]

I also updated log4j-appserver/src/site/markdown/index.md.vm

Thank you!
Gary

On Mon, Nov 13, 2017 at 8:04 AM, Gary Gregory 
wrote:

> Oh, I added a section to the main index:
>
> #h3 Integrating with Application Servers
>
> Version 2.10.0 introduces a the module log4j-appserver to improve
> integration with Apache Tomcat and Eclipse Jetty.
>
> Gary
>
> On Sun, Nov 12, 2017 at 10:10 AM, Mikael Ståldal  wrote:
>
>> On 2017-11-12 16:00, Gary Gregory wrote:
>>
>>> On Sun, Nov 12, 2017 at 7:25 AM, Mikael Ståldal 
>>> wrote:
>>>
>>> Do we want a package-info.java in the Jetty package, like in the Tomcat
 package?

 And you should probably add a section about Jetty integraion in
 log4j-appserver/src/site/markdown/index.md.vm

>>>
>>> Done. Please review.
>>>
>>
>> I don't see anything about Jetty in log4j-appserver/src/site/markd
>> own/index.md.vm
>>
>>
>

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

[Ralph Goers]

Are you planning on fixing this?

Ralph

> On Nov 11, 2017, at 5:15 PM, Ralph Goers  wrote:
> 
> Because the caller of newLogger(name) is AbstractLogger its ClassLoader will 
> always be used. You need the ClassLoader of the caller of getLogger().
> 
> Ralph
> 
>> On Nov 11, 2017, at 3:43 PM, Gary Gregory  wrote:
>> 
>> Please code review git master. I'm not sure I have the class loader right.
>> 
>> Gary
>> 
>> On Sat, Nov 11, 2017 at 2:54 PM, Ralph Goers 
>> wrote:
>> 
>>> Oh, but you probably don’t want to extend AbstractLogger. You really want
>>> the FQCN of the caller to be able to identify the ClassLoader and
>>> LoggerContext to use and you won’t get that from AbstractLogger’s getLogger
>>> method.
>>> 
>>> Ralph
>>> 
 On Nov 11, 2017, at 2:45 PM, Ralph Goers 
>>> wrote:
 
 Sure. Look at TomcatLogger. It does exactly what you are trying to do.
 
 Ralph
 
> On Nov 11, 2017, at 2:02 PM, Gary Gregory 
>>> wrote:
> 
> The Javadoc for Log4j's LoggerAdapter says "This registry should not be
> used for Log4j Loggers; it is instead used for creating bridges to other
> external log systems.".
> 
> In this case we are not bridging TO another log system. We are plugging
> INTO Jetty's log system and subclassing Jetty's own LoggerAdapter class
> (out convenience.)
> 
> Further thoughts?
> 
> Gary
> 
> On Fri, Nov 10, 2017 at 9:25 PM, Matt Sicker  wrote:
> 
>> IIRC, the easiest way to support it might be to use
>> https://logging.apache.org/log4j/2.x/log4j-api/apidocs/
>> org/apache/logging/log4j/spi/AbstractLoggerAdapter.html
>> 
>> On 10 November 2017 at 22:16, Gary Gregory 
>>> wrote:
>> 
>>> I think you are correct...
>>> 
>>> Gary
>>> 
>>> On Fri, Nov 10, 2017 at 6:59 PM, Matt Sicker 
>>> wrote:
>>> 
 Wouldn't this implementation contain incorrect caller location
>>> information?
 
 On 10 November 2017 at 19:25,  wrote:
 
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master aad2f132b -> 7d52f131e
> 
> 
> [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse
>>> Jetty's
> org.eclipse.jetty.util.log.Logger.
> 
> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/
> commit/7d52f131
> Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/
 7d52f131
> Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/
 7d52f131
> 
> Branch: refs/heads/master
> Commit: 7d52f131ec1e000834bcb40343f3f2d41805c75a
> Parents: aad2f13
> Author: Gary Gregory 
> Authored: Fri Nov 10 18:25:47 2017 -0700
> Committer: Gary Gregory 
> Committed: Fri Nov 10 18:25:47 2017 -0700
> 
> 
>> --
> log4j-appserver/pom.xml |   8 +
> .../log4j/appserver/jetty/Log4j2Logger.java | 184
 +++
> src/changes/changes.xml |   3 +
> 3 files changed, 195 insertions(+)
> 
>> --
> 
> 
> http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/
> 7d52f131/log4j-appserver/pom.xml
> 
>> --
> diff --git a/log4j-appserver/pom.xml b/log4j-appserver/pom.xml
> index e96b1fc..6acd77b 100644
> --- a/log4j-appserver/pom.xml
> +++ b/log4j-appserver/pom.xml
> @@ -34,6 +34,7 @@
>  Web Documentation
>  /log4j-appserver
>  8.5.20
> +8.2.0.v20160908 
>  org.apache.logging.log4j.appserver
> 
> 
> @@ -56,6 +57,7 @@
>org.apache.tomcat
>tomcat-catalina
>${tomcat.version}
> +  provided
>
>  
>org.apache.tomcat
> @@ -71,6 +73,12 @@
>  
>
>  
> +
> +  org.eclipse.jetty
> +  jetty-util
> +  ${jetty.version}
> +  provided
> +
> 
>  
>  
> 
> http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/
> 7d52f131/log4j-appserver/src/main/java/org/apache/logging/
> log4j/appserver/jetty/Log4j2Logger.java
> 

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

[Gary Gregory]

Oh, I added a section to the main index:

#h3 Integrating with Application Servers

Version 2.10.0 introduces a the module log4j-appserver to improve
integration with Apache Tomcat and Eclipse Jetty.

Gary

On Sun, Nov 12, 2017 at 10:10 AM, Mikael Ståldal  wrote:

> On 2017-11-12 16:00, Gary Gregory wrote:
>
>> On Sun, Nov 12, 2017 at 7:25 AM, Mikael Ståldal  wrote:
>>
>> Do we want a package-info.java in the Jetty package, like in the Tomcat
>>> package?
>>>
>>> And you should probably add a section about Jetty integraion in
>>> log4j-appserver/src/site/markdown/index.md.vm
>>>
>>
>> Done. Please review.
>>
>
> I don't see anything about Jetty in log4j-appserver/src/site/markd
> own/index.md.vm
>
>