Re: Docs?

ding list of TODOs is > to update the way those docs are generated, using new tooling, so perhaps the > docs (a) could be auto-generated and (b) will look a little nicer. > > Can I just update my `asf-site` branch and push? no need for review, surely? > > -d > > On 2022-11-

Re: Docs?

lph > On Nov 16, 2022, at 9:08 PM, Davyd McColl wrote: > > Ralph, I'd appreciate any help here. Seems there's a permissions error or > something - sdk docs links return a 403. > > -d > > > On 16 November 2022 23:22:26 Alex Winfield <7nil...@gmail.com> wrote: &g

Re: Docs?

Ralph, I'd appreciate any help here. Seems there's a permissions error or something - sdk docs links return a 403. -d On 16 November 2022 23:22:26 Alex Winfield <7nil...@gmail.com> wrote: Where should I look for the docs? All of the examples point to dead links: https://logging.apac

Docs?

Where should I look for the docs? All of the examples point to dead links: https://logging.apache.org/log4net/release/config-examples.html Sample code online doesn't appear to actually work (%aspnet-context appears to be parsed as just %a, with "spnet-context" as a static string).

Re: A little stuck with publishing updated site / docs for log4net 2.0.9

I have updated the logging services site and corrected log4net’s .htaccess file to point to the 2.0.9 release. However, I cannot seem to get the download page to reference 2.0.9. It still shows 2.0.8. The release notes are correct though. Ralph > On Aug 28, 2020, at 7:38 AM, Davyd McColl

Re: A little stuck with publishing updated site / docs for log4net 2.0.9

Thanks -d On 2020/08/28 16:07:45, Apache wrote: I will take care of the main logging site. It currently uses the ASF CMS but we have to get off of it so there isn’t much point in you having to learn how to deal with it. Ralph > On Aug 28, 2020, at 12:26 AM, Davyd McColl wrote: > > Hi all >

Re: A little stuck with publishing updated site / docs for log4net 2.0.9

I will take care of the main logging site. It currently uses the ASF CMS but we have to get off of it so there isn’t much point in you having to learn how to deal with it. Ralph > On Aug 28, 2020, at 12:26 AM, Davyd McColl wrote: > > Hi all > > I've been trying to update content for

A little stuck with publishing updated site / docs for log4net 2.0.9

Hi all I've been trying to update content for http://logging.apache.org/log4net (in particular http://logging.apache.org/log4net/release) and I'm sure I'm just doing something silly or missing something. I've followed instructions at 

Re: [log4j2] Legacy docs

I did not realize the sites were archived. That's great. We only need to document that fact and link. Gary On Jun 25, 2017 21:57, "Ralph Goers" wrote: The Legacy section on the left nav bar contains a link for Log4j 1.x and Log4j 2.3. These two releases (and sites)

Re: [log4j2] Legacy docs

The Legacy section on the left nav bar contains a link for Log4j 1.x and Log4j 2.3. These two releases (and sites) have special significance. No other releases do. They should not be lost in a sea of other releases. Plus, it would make that left navigation extremely long. Although all the

Re: [log4j2] Legacy docs

Hi, You're talking about something different, the change reports are one thing, the site is another. I am thinking of users that are stuck on an old random release either by direct or transitive dependency. Using the site that matches their version would be quite helpful. No urgent of course.

Re: [log4j2] Legacy docs

I only created that so people would be able to find release 2.3 if they needed to use Java 6. My fear is that if we add all the releases there then that will get lost in the noise. BTW - all the releases are listed at http://logging.apache.org/log4j/2.x/changes-report.html

[log4j2] Legacy docs

Hi All, We have a nice "Legacy" section of our site. I think we should track every release there. 2c, Gary

Re: Garbage-free Log4j docs preview

Sent from my iPhone > On 2016/06/07, at 0:16, Gary Gregory wrote: > > > On Jun 6, 2016 6:48 AM, "Remko Popma" wrote: > > > > > > > > On Monday, June 6, 2016 at 6:16:52 PM UTC+9, Anthony Maire wrote: > >> > >> Hi Remko > >> > >> Great job ! >

Re: Garbage-free Log4j docs preview

On Jun 6, 2016 6:48 AM, "Remko Popma" wrote: > > > > On Monday, June 6, 2016 at 6:16:52 PM UTC+9, Anthony Maire wrote: >> >> Hi Remko >> >> Great job ! >> As Martin said, it's really a good thing for the high-performance community that someone is trying to improve existing

Re: Garbage-free Log4j docs preview

On Monday, June 6, 2016 at 6:16:52 PM UTC+9, Anthony Maire wrote: > > Hi Remko > > Great job ! > As Martin said, it's really a good thing for the high-performance > community that someone is trying to improve existing logging frameworks. > The company I'm working for even started to write it's

Re: Garbage-free Log4j docs preview

fer); >> } >> >> >> We chose StringBuilder because the Appendable API is not rich enough. >> Any Object that is logged, either standalone or as a parameter, if it >> does not implement CharSequence but it does >> implement StringBuilderFormattable then Log4j 2.6

Re: Garbage-free Log4j docs preview

On Friday, June 3, 2016 at 4:42:51 PM UTC+9, Philippe Marschall wrote: > > > > On Tuesday, May 17, 2016 at 7:13:09 PM UTC+2, Remko Popma wrote: >> >> Hi all, >> >> First, my thanks to the many people who gave helpful advice and feedback >> on how to measure Log4j response time on this list some

Re: Garbage-free Log4j docs preview

On Thu, May 26, 2016 at 11:33 AM, Matt Sicker wrote: > There's a bson dependency in log4j-nosql as well (from mongo). > Right, the wire format for MongoDB is BSON IIRC. Gary > > On 26 May 2016 at 11:46, Gary Gregory wrote: > >> I think we can

Re: Garbage-free Log4j docs preview

There's a bson dependency in log4j-nosql as well (from mongo). On 26 May 2016 at 11:46, Gary Gregory wrote: > I think we can support BSON through Jackson. That would be interesting for > 2.7. > > Gary > On May 26, 2016 6:47 AM, "Remko Popma"

Re: Garbage-free Log4j docs preview

I think we can support BSON through Jackson. That would be interesting for 2.7. Gary On May 26, 2016 6:47 AM, "Remko Popma" wrote: > Kirk, > > Logging in binary format has been on my todo list for a while. > We did some preliminary analysis here: >

Re: Garbage-free Log4j docs preview

I just tried, gives a 5x performance boost. See Git branch LOG4J2-1395 . On Tue, May 24, 2016 at 4:27 PM, Mikael Ståldal wrote: > Could we avoid that by using FileDescriptor.out / FileDescriptor.err > instead of

Re: Garbage-free Log4j docs preview

I used no special config for the JMH benchmarks, so the ConsoleAppender writes to the terminal. Perhaps it is a good idea to suggest redirecting to a file in the text that accompanies these benchmark results. Or add a benchmark result for how fast ConsoleAppender is when redirected. On Thu, May

Re: Garbage-free Log4j docs preview

Did you redirect standard out to a file, or did you let it write to the terminal, when running the Log4j2AppenderComparisonBenchmark? I just tried both, and that gives you a significant 5-10x difference. On Tue, May 17, 2016 at 7:13 PM, Remko Popma wrote: > Hi all, > >

Re: Garbage-free Log4j docs preview

Kirk, Logging in binary format has been on my todo list for a while. We did some preliminary analysis here: https://issues.apache.org/jira/browse/LOG4J2-1305 Your thoughts on this effort would be much appreciated. Remko On Thursday, May 26, 2016 at 5:32:27 PM UTC+9, Kirk Pepperdine wrote: > >

Re: Garbage-free Log4j docs preview

http://12factor.net/logs (I don't fully agree with this, but it would be nice if we can support it in an efficient way.) On Wed, May 25, 2016 at 6:50 PM, Matt Sicker wrote: > Plus there's the fact that some people are encouraging all logging to > happen to stdout (in

Re: Garbage-free Log4j docs preview

Plus there's the fact that some people are encouraging all logging to happen to stdout (in containers) for simpler log configuration and handling. It would be nice if we can support that scenario better. On 25 May 2016 at 09:18, Mikael Ståldal wrote: > There are use

Re: Garbage-free Log4j docs preview

There are use cases for logging to standard out/err and redirecting to a file or something else than an actual console. It would be good if we would optimize so that is not 50x slower than logging directly to file. On Wed, May 25, 2016 at 4:09 PM, Remko Popma wrote: > > >

Re: Garbage-free Log4j docs preview

On Wednesday, May 25, 2016 at 3:02:33 AM UTC+9, Richard Warburton wrote: > > Hi, > > Could we avoid that by using FileDescriptor.out / FileDescriptor.err >> instead of System.out / System.err ? >> >> On Tue, May 24, 2016 at 4:09 PM, Matt Sicker > > wrote: >> >>> All the

Re: Garbage-free Log4j docs preview

It may be that the spec says the FileDescriptor has to point at a FileInputStream, in which case System.out would have to wrap it. Ralph > On May 25, 2016, at 5:43 AM, Ralph Goers wrote: > > You are missing the point. What does IBM's JDK do? What does the gnu JDK

Re: Garbage-free Log4j docs preview

You are missing the point. What does IBM's JDK do? What does the gnu JDK do? What does Android do? You can only rely on what the spec says. I haven't read the spec, but the javadoc certainly says nothing. Ralph > On May 25, 2016, at 4:09 AM, Mikael Ståldal

Re: Garbage-free Log4j docs preview

http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/lang/System.java#1087 On Wed, May 25, 2016 at 12:51 PM, Ralph Goers wrote: > I haven't looked at the source, but the point is that FileDescriptor gives > no guarantees what it is

Re: Garbage-free Log4j docs preview

I haven't looked at the source, but the point is that FileDescriptor gives no guarantees what it is referencing. Sent from my iPad > On May 25, 2016, at 12:49 AM, Mikael Ståldal > wrote: > > > but I would guess the the FileDescriptor may just be a reference to the

Re: Garbage-free Log4j docs preview

> but I would guess the the FileDescriptor may just be a reference to the PrintStream. I think it's the other way around, System.out is a wrapper around FileDescriptor.out. Look at the source code for java.lang.System in JDK 8. On Tue, May 24, 2016 at 7:53 PM, Ralph Goers

Re: Garbage-free Log4j docs preview

On Wednesday, May 25, 2016 at 3:25:00 AM UTC+9, Benedict Elliott Smith wrote: > > There is a "major" downside for some users - as an example, imagine a user > with a single core server that performs a high rate of logging, and does so > once every 100us. This user is interested in throughput

Re: Garbage-free Log4j docs preview

The javadoc for FileDescriptor is fairly ambiguous. I’d have to look at the code, but I would guess the the FileDescriptor may just be a reference to the PrintStream. I really don’t think you can count on what it points to. I would also worry about us trying to use the FileDescriptor while the

Re: Garbage-free Log4j docs preview

On Tuesday, May 24, 2016 at 11:27:33 PM UTC+9, Mikael Ståldal wrote: > > Could we avoid that by using FileDescriptor.out / FileDescriptor.err > instead of System.out / System.err ? > > On Tue, May 24, 2016 at 4:09 PM, Matt Sicker > wrote: > >> All the PrintStream.write()

Re: Garbage-free Log4j docs preview

On Tuesday, May 24, 2016 at 6:13:37 PM UTC+9, Benedict Elliott Smith wrote: > > But "response time pauses" are only an issue if you are latency sensitive, > which was one of my explicit criteria. Most users aren't latency sensitive. > > Holding a lock is not inherently expensive; in fact it is

Re: Garbage-free Log4j docs preview

But wouldn't that mess up output when another thread does sys out println? Or do we hook in to System.setOut and setErr? Gary On May 24, 2016 7:27 AM, "Mikael Ståldal" wrote: > Could we avoid that by using FileDescriptor.out / FileDescriptor.err > instead of

Re: Garbage-free Log4j docs preview

Could we avoid that by using FileDescriptor.out / FileDescriptor.err instead of System.out / System.err ? On Tue, May 24, 2016 at 4:09 PM, Matt Sicker wrote: > All the PrintStream.write() methods have locks. > > On 24 May 2016 at 02:56, Mikael Ståldal

Re: Garbage-free Log4j docs preview

All the PrintStream.write() methods have locks. On 24 May 2016 at 02:56, Mikael Ståldal wrote: > Do we know why Console has so bad performance (compared to File)? Is this > true also if you redirect STDOUT to a file? > > On Tue, May 17, 2016 at 7:13 PM, Remko Popma

Re: Garbage-free Log4j docs preview

Do we know why Console has so bad performance (compared to File)? Is this true also if you redirect STDOUT to a file? On Tue, May 17, 2016 at 7:13 PM, Remko Popma wrote: > Hi all, > > First, my thanks to the many people who gave helpful advice and feedback > on how to

Re: Garbage-free Log4j docs preview

> But I don't understand why users should only configure async logging in rare cases? Synchronous logging also involves holding a lock. Log4j 2 makes an effort to release this lock as soon as > possible (locking only while copying a byte array from a thread-local buffer to the I/O device), but as

Re: Garbage-free Log4j docs preview

Can the support for Intel TSX in Java 8u20 be relevant here? https://bugs.openjdk.java.net/browse/JDK-8031320 On Sun, May 22, 2016 at 3:42 PM, Remko Popma wrote: > > > On Sunday, May 22, 2016 at 6:34:13 PM UTC+9, Benedict Elliott Smith wrote: >> >> Hi Remko, >> >> I

Re: Garbage-free Log4j docs preview

> But I don't understand why users should only configure async logging in rare cases? Synchronous logging also involves holding a lock. Log4j 2 makes an effort to release this lock as soon as > possible (locking only while copying a byte array from a thread-local buffer to the I/O device), but as

Re: Garbage-free Log4j docs preview

Yes, potentially *very* relevant! Please post this on the mechanical sympathy mailing list! On Monday, 23 May 2016, Mikael Ståldal wrote: > Can the support for Intel TSX in Java 8u20 be relevant here? > > https://bugs.openjdk.java.net/browse/JDK-8031320 > > On Sun,

Re: Garbage-free Log4j docs preview

On Monday, May 23, 2016 at 2:47:05 AM UTC+9, Benedict Elliott Smith wrote: > > Your pride should be saved by your gracious recognition of the error :) > > > However this is the core of my point: you’re clearly an intelligent, > conscientious and talented developer, and yet you did not fully

Re: Garbage-free Log4j docs preview

Can the support for Intel TSX in Java 8u20 be relevant here? https://bugs.openjdk.java.net/browse/JDK-8031320 On Sun, May 22, 2016 at 5:40 PM, Remko Popma wrote: > > > On Sunday, May 22, 2016 at 11:08:37 PM UTC+9, Benedict Elliott Smith wrote: >> >> It's possible I'm

Re: Garbage-free Log4j docs preview

On Sunday, May 22, 2016 at 11:08:37 PM UTC+9, Benedict Elliott Smith wrote: > > It's possible I'm missing some other aspect that insulates the application > thread from the disruptor, but from your message it seems to me that you > fall into the all-too-common category of people who do not

Re: Garbage-free Log4j docs preview

It's possible I'm missing some other aspect that insulates the application thread from the disruptor, but from your message it seems to me that you fall into the all-too-common category of people who do not fully understand the semantics of the disruptor. Application threads (i.e. disruptor

Re: Garbage-free Log4j docs preview

On Sunday, May 22, 2016 at 6:34:13 PM UTC+9, Benedict Elliott Smith wrote: > > Hi Remko, > > I realise that I was looking at the old log4j code without realising it, > in which there is always a futex involved. > Which class is this? Async Loggers in Log4j 2 have always been lock-free. What

Re: Garbage-free Log4j docs preview

After looking more closely I found that the org.slf4j.spi.LocationAwareLogger::log method is currently not implemented in a

Re: Garbage-free Log4j docs preview

On Thursday, May 19, 2016 at 11:10:45 AM UTC+9, Jerry Shea wrote: > This is fantastic, thanks for this Remko. > > > Can I ask a couple of questions? > 1. is log4j 2.6 designed to operate garbage-free when used as an SLF4J > implementation too, or only with the native API? The log4j-slf4j-impl

Re: Garbage-free Log4j docs preview

Thank you Martin, appreciated! :-) On Wednesday, May 18, 2016 at 2:33:55 AM UTC+9, Martin Thompson wrote: > > Hi Remko, > > I'd just like to say that it is a great service to the community as a > whole that someone is seriously looking at improving logging. > > If you keep it up you'll be

Re: Garbage-free Log4j docs preview

I see. I was under the impression that the Filter checked by Logger.isEnabled() was a composite of the global filters and the Logger filter, but I just assumed and never really checked. Thanks for correcting me. Yes, I agree this is a good idea for a future enhancement. I don't know how often

Re: Garbage-free Log4j docs preview

That is only checking the global filters. Filters can also be on the Logger (or more accurately, the LoggerConfig), AppenderRef, or Appender. I don’t think it would ever work to check the filters on the appenders, but I would think it would be possible to check those on the Logger and possibly

Re: Garbage-free Log4j docs preview

Remko, Benedict makes a good point. While I don’t think filters on appenders should be called before putting events on the queue we should probably be executing the filters on the Logger. But currently those are called in the LoggerConfig, which I think is after the events are added to the

Re: Garbage-free Log4j docs preview

Could I suggest that you run tests for latency and throughput effects of using this in systems with only moderate-to-low numbers of logging calls? (i.e. the vast majority of systems!) It's very likely that in such systems messages will not reach a velocity to keep the Dispatcher running, and so

Re: Garbage-free Log4j docs preview

To log4j-dev: FYI the Mechanical Sympathy Google group is where a number of Java performance experts hang out. My previous post there was: https://groups.google.com/forum/m/#!topic/mechanical-sympathy/HwTrOMnm6h0 Remko On Wednesday, 18 May 2016, Remko Popma wrote: > Hi

Garbage-free Log4j docs preview

Hi all, First, my thanks to the many people who gave helpful advice and feedback on how to measure Log4j response time on this list some time ago. We're about to start the Log4j 2.6 release. If anyone is interested, a preview of the garbage-free logging manual page is here:

Re: Bad PatternLayout site docs

pattern}" in > the 2nd row should not use bold font. > > Sent from my iPhone > > On 2015/10/01, at 1:43, Gary Gregory <garydgreg...@gmail.com> wrote: > > The site docs at > https://logging.apache.org/log4j/2.x/manual/layouts.html#PatternLayout > > shows this co

Re: Bad PatternLayout site docs

ydgreg...@gmail.com> wrote: > > The site docs at > https://logging.apache.org/log4j/2.x/manual/layouts.html#PatternLayout > > shows this conversion pattern twice: > > enc{pattern} > encode{pattern> > > and > > enc{pattern} > encode{pattern} &g

Bad PatternLayout site docs

The site docs at https://logging.apache.org/log4j/2.x/manual/layouts.html#PatternLayout shows this conversion pattern twice: enc{pattern} encode{pattern> and enc{pattern} encode{pattern} Something's not right! :-( -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persiste

[jira] [Created] (LOG4NET-459) Generated API docs are unreadable

Berin Loritsch created LOG4NET-459: -- Summary: Generated API docs are unreadable Key: LOG4NET-459 URL: https://issues.apache.org/jira/browse/LOG4NET-459 Project: Log4net Issue Type: Bug

[jira] [Resolved] (LOG4J2-946) [docs] Using Log4j 2 in Web Applications: Update example (Log4jWebLifeCycle is not visible)

[ https://issues.apache.org/jira/browse/LOG4J2-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-946. - Resolution: Fixed Fix Version/s: 2.2 Fixed docs in git master. Please verify that the new

[jira] [Updated] (LOG4J2-946) [docs] Log4jWebLifeCycle is not visible

[ https://issues.apache.org/jira/browse/LOG4J2-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-946: Summary: [docs] Log4jWebLifeCycle is not visible (was: Log4jWebLifeCycle is not visible) [docs

[jira] [Comment Edited] (LOG4J2-946) [docs] Using Log4j 2 in Web Applications: Update example (Log4jWebLifeCycle is not visible)

: -- The docs are wrong, it was not updated to the latest version of {{org.apache.logging.log4j.web.TestAsyncServlet}} (see git). Just change {{Log4jWebLifeCycle}} to {{Log4jWebSupport}}: {code:java} final Log4jWebSupport webLifeCycle = WebLoggerContextUtils.getWebLifeCycle

[jira] [Updated] (LOG4J2-946) [docs] Using Log4j 2 in Web Applications: Update example (Log4jWebLifeCycle is not visible)

[ https://issues.apache.org/jira/browse/LOG4J2-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-946: Summary: [docs] Using Log4j 2 in Web Applications: Update example (Log4jWebLifeCycle is not visible

[jira] [Updated] (LOG4J2-901) Update docs for SyslogAppender: No structured id name was supplied

[ https://issues.apache.org/jira/browse/LOG4J2-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-901: Summary: Update docs for SyslogAppender: No structured id name was supplied (was: SyslogAppender

[jira] [Resolved] (LOG4J2-901) Update docs for SyslogAppender: No structured id name was supplied

[ https://issues.apache.org/jira/browse/LOG4J2-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-901. - Resolution: Fixed Fix Version/s: 2.2 Docs updated. Site needs to be regenerated. Update

GELF site docs

FYI: I updated the site in master for GELF. Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch in Action

Re: Docs and Subversion

:00) /divdivTo: Log4J Developers List log4j-dev@logging.apache.org /divdivSubject: Re: Docs and Subversion /divdiv /divWhich doc pages? Sent from my iPhone On 2014/09/19, at 20:11, Gary Gregory garydgreg...@gmail.com wrote: Just a TODO here that the wiki and some doc pages still refer

Re: Docs and Subversion

Which doc pages? Sent from my iPhone On 2014/09/19, at 20:11, Gary Gregory garydgreg...@gmail.com wrote: Just a TODO here that the wiki and some doc pages still refer to Subversion. Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second

Docs and Subversion

Just a TODO here that the wiki and some doc pages still refer to Subversion. Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition http://www.manning.com/bauer3/ JUnit in Action, Second Edition http://www.manning.com/tahchiev/ Spring Batch

Re: Docs changelog entry for IO Streams module

any docs yet. I added a link to the left-hand side nav menu, but there is nothing to link to... Also we need an entry in changes.xml so this feature gets mentioned in the release notes. Should we create a Jira that explains the motivation for this feature? Remko

Re: [1/4] git commit: Update JUL bridge docs.

Thanks! I just realized that if a JUL custom level is used without specifying a LevelConverter, it's actually not a problem: the Logger's level will be null and it will just use the log level of its parent (that's a fairly recent change, I think)! Is it worth mentioning that in the docs

Re: [1/4] git commit: Update JUL bridge docs.

the log level of its parent (that's a fairly recent change, I think)! Is it worth mentioning that in the docs? Sent from my iPhone On 2014/09/19, at 7:47, mattsic...@apache.org wrote: Repository: logging-log4j2 Updated Branches: refs/heads/master b1783a0aa - c8406750d Update JUL

Docs changelog entry for IO Streams module

Looks like the IO Streams module does not have any docs yet. I added a link to the left-hand side nav menu, but there is nothing to link to... Also we need an entry in changes.xml so this feature gets mentioned in the release notes. Should we create a Jira that explains the motivation

Re: Docs changelog entry for IO Streams module

I thought there was at least 1 Jira related to this that spawned the whole adventure. Ralph On Sep 16, 2014, at 9:42 AM, Remko Popma remko.po...@gmail.com wrote: Looks like the IO Streams module does not have any docs yet. I added a link to the left-hand side nav menu, but there is nothing

Re: Docs changelog entry for IO Streams module

, Remko Popma remko.po...@gmail.com javascript:; wrote: Looks like the IO Streams module does not have any docs yet. I added a link to the left-hand side nav menu, but there is nothing to link to... Also we need an entry in changes.xml so this feature gets mentioned in the release notes

Re: Docs changelog entry for IO Streams module

there was at least 1 Jira related to this that spawned the whole adventure. Ralph On Sep 16, 2014, at 9:42 AM, Remko Popma remko.po...@gmail.com wrote: Looks like the IO Streams module does not have any docs yet. I added a link to the left-hand side nav menu, but there is nothing to link

Re: Docs changelog entry for IO Streams module

. Ralph On Sep 16, 2014, at 9:42 AM, Remko Popma remko.po...@gmail.com wrote: Looks like the IO Streams module does not have any docs yet. I added a link to the left-hand side nav menu, but there is nothing to link to... Also we need an entry in changes.xml so this feature gets mentioned

[jira] [Created] (LOG4J2-740) Invalid servlet configuration in docs

Kosta Krauth created LOG4J2-740: --- Summary: Invalid servlet configuration in docs Key: LOG4J2-740 URL: https://issues.apache.org/jira/browse/LOG4J2-740 Project: Log4j 2 Issue Type

[jira] [Resolved] (LOG4J2-740) Invalid servlet configuration in docs

, revision 1613337. Please verify and close. Invalid servlet configuration in docs - Key: LOG4J2-740 URL: https://issues.apache.org/jira/browse/LOG4J2-740 Project: Log4j 2 Issue Type: Documentation

[jira] [Updated] (LOG4J2-631) Update docs to clarify how to use formatter logger and standard logger together

: Update docs to clarify how to use formatter logger and standard logger together (was: Cannot use formatter logger and standard logger with same name) Changed title to reflect the remaining task. Update docs to clarify how to use formatter logger and standard logger together

[jira] [Resolved] (LOG4J2-631) Update docs to clarify how to use formatter logger and standard logger together

[ https://issues.apache.org/jira/browse/LOG4J2-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-631. Resolution: Fixed Fixed in revision 1609755. Please verify and close. Update docs to clarify how

JMX and docs

Hi all: Reading https://issues.apache.org/jira/browse/LOG4J2-423 I wonder how to best document JMX. Should each feature (like each appenders) (1) document what it exposes through JMX, or, (2) should the JMX section list all that is exposed. I'm thinking (1). Gary -- E-Mail:

Re: JMX and docs

What kind of docs do you have in mind? The JMX API is documented in detail here: http://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/jmx/package-summary.html In addition to API, the JMX section has pointers for connectivity, and of course docs for the GUI

Re: JMX and docs

On Wed, Oct 16, 2013 at 9:44 AM, Remko Popma remko.po...@gmail.com wrote: What kind of docs do you have in mind? Well, I suppose we have it covered by this blanket statement: Appenders are instrumented with MBeans and can be remotely monitored and controlled. I was just wondering if it would

Re: JMX and docs

On Wednesday, October 16, 2013, Gary Gregory wrote: On Wed, Oct 16, 2013 at 9:44 AM, Remko Popma remko.po...@gmail.comjavascript:_e({}, 'cvml', 'remko.po...@gmail.com'); wrote: What kind of docs do you have in mind? Well, I suppose we have it covered by this blanket statement: Appenders

Re: docs

Please refer to below URL for the moment. https://svn.apache.org/repos/asf/logging/site/trunk/docs/log4cxx/apidocs/index.html regards, *Chand Priyankara* [image: Facebook]http://www.facebook.com/chand.priyankara [image: LinkedIn] http://lk.linkedin.com/in/chandpriyankara [image: Blogger

Re: small patch: Fix install location for docs

Sorry for posting a patch on users@. I created a Jira Issue [1] and attached the patch. Thx, Alex [1] https://issues.apache.org/jira/browse/LOGCXX-414 On Wed, Jun 26, 2013 at 6:02 PM, Alexandru Zbârcea zbarce...@gmail.comwrote: Hi, As stated by:

small patch: Fix install location for docs

Hi, As stated by: http://www.gnu.org/software/automake/manual/automake.html Documentation files should go to *docdir* and not to *pkgdatadir*. Hope it helps, Alex fix-install-location-for-docs.patch Description: Binary data

[jira] [Commented] (LOG4J2-73) docs: download site and how to use RolloverStrategy.

[ https://issues.apache.org/jira/browse/LOG4J2-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672087#comment-13672087 ] Tushar commented on LOG4J2-73: -- thank you docs: download site and how to use

[jira] [Closed] (LOG4J2-73) docs: download site and how to use RolloverStrategy.

[ https://issues.apache.org/jira/browse/LOG4J2-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar closed LOG4J2-73. docs: download site and how to use RolloverStrategy

[jira] [Closed] (LOG4J2-87) docs in zip and pdf

[ https://issues.apache.org/jira/browse/LOG4J2-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar closed LOG4J2-87. thank you docs in zip and pdf --- Key: LOG4J2-87

[jira] [Resolved] (LOG4J2-87) docs in zip and pdf

of the user's guide. The release instructions at http://wiki.apache.org/logging/Log4j2ReleaseGuide now include instructions to publish the zip of the site. docs in zip and pdf --- Key: LOG4J2-87 URL: https://issues.apache.org/jira

[jira] [Closed] (LOG4J2-90) docs - tip for -server

[ https://issues.apache.org/jira/browse/LOG4J2-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar closed LOG4J2-90. docs - tip for -server -- Key: LOG4J2-90 URL: https

[jira] [Resolved] (LOG4J2-90) docs - tip for -server

to the performance page. docs - tip for -server -- Key: LOG4J2-90 URL: https://issues.apache.org/jira/browse/LOG4J2-90 Project: Log4j 2 Issue Type: Improvement Components: Documentation Environment

[jira] [Created] (LOG4J2-90) docs - tip for -server

Tushar created LOG4J2-90: Summary: docs - tip for -server Key: LOG4J2-90 URL: https://issues.apache.org/jira/browse/LOG4J2-90 Project: Log4j 2 Issue Type: Improvement Components

  1   2   3   >