Re: FileAppenderBenchmark

While I couldn’t get it to work with Log4j 2.8 the results I get for 2.7 do not match Ceki’s at all. These are the results for Java 7: Benchmark Mode SamplesScoreError Units o.a.l.l.p.j.FileAppenderBenchmark.julFile

Re: FileAppenderBenchmark

That error is exactly what I am seeing. For some reason the class files under log4j-perf\target\generated-sources\annotations (generated by JMH) are not included in the shaded benchmarks.jar or in log4j-perf-2.8.1-SNAPSHOT.jar... Thanks for mentioning that it works with 2.7. That means it is likel

Re: FileAppenderBenchmark

Ralph, are your benchmark results with 4 threads (-t 4)? On Sun, Jan 29, 2017 at 5:51 PM, Apache wrote: > While I couldn’t get it to work with Log4j 2.8 the results I get for 2.7 > do not match Ceki’s at all. These are the results for Java 7: > > Benchmark

[jira] (LOG4J2-1561) print expected mdc info to each line of the exception stacktrace

Title: Message Title ASF GitHub Bot commented on LOG4J2-1561

Re: FileAppenderBenchmark

The cause seems to be a change in the master pom: the maven-compiler-plugin plugin now has the below section which was not there in 2.7. If I take it out and build only log4j-perf, the benchmarks run without error. (But building all modules fails: some problem in log4j-core...)

Re: FileAppenderBenchmark

Yes. Ralph > On Jan 28, 2017, at 11:59 PM, Remko Popma wrote: > > Ralph, are your benchmark results with 4 threads (-t 4)? > >> On Sun, Jan 29, 2017 at 5:51 PM, Apache wrote: >> While I couldn’t get it to work with Log4j 2.8 the results I get for 2.7 do >> not match Ceki’s at all. These are

[jira] (LOG4J2-1561) print expected mdc info to each line of the exception stacktrace

Title: Message Title ASF GitHub Bot commented on LOG4J2-1561

Re: logging-log4j-scala git commit: Update README to be similar to logging-log4j2

Thanks! That's what I get for copying things from Commons instead of writing them myself! :P On 28 January 2017 at 18:25, Remko Popma wrote: > Spelling nag: > discuss you're changes -> your > (Contributing.md) > > > (Away from pc) Remko > > Sent from my iPhone > > > On Jan 29, 2017, at 4:13, mat

Re: logging-log4j-scala git commit: Add intro to README

I noticed that right after I pushed it. Fixed in subsequent commit, thanks. On 28 January 2017 at 18:47, Remko Popma wrote: > Spelling nag: > introduced as in Log4j 2.8.1 -> introduced in > > Sent from my iPhone > > > On Jan 29, 2017, at 4:27, mattsic...@apache.org wrote: > > > > introduced > >

Re: FileAppenderBenchmark

That maven-compiler-plugin config was originally only included in log4j-core in order to allow the PluginProcessor annotation processor to re-run against log4j-core without needing to split it into its own jar. I'm not sure why it's configured for everything now. On 29 January 2017 at 08:59, Ralph

[jira] (LOG4J2-1431) Simplify log4j system property naming scheme

Title: Message Title Matt Sicker commented on LOG4J2-1431

Re: logging-log4j-scala git commit: Update README to be similar to logging-log4j2

I fixed that typo in the commons-build-plugin template as well. Looks like all the Commons projects have that exact typo! On 29 January 2017 at 10:52, Matt Sicker wrote: > Thanks! That's what I get for copying things from Commons instead of > writing them myself! :P > > On 28 January 2017 at 18:

[jira] (LOG4J2-1802) Convert documentation into Markdown

Title: Message Title Matt Sicker created an issue

Jenkins build is still unstable: Log4j 2.x #2635

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Jenkins build is back to stable : Log4j 2.x #2636

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Build failed in Jenkins: Log4j 2.x #2637

See Changes: [Matt Sicker] Refactor dependency output into macros [Matt Sicker] Add maven/gradle/sbt instructions for using snapshots repository -- [...truncated 9875 lines...] Tests run: 59, Failu

Jenkins build is back to normal : Log4j 2.x #2638

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] (LOG4J2-1802) Convert documentation into Markdown

Title: Message Title ASF subversion and git services commented on LOG4J2-1802

Build failed in Jenkins: Log4j 2.x #2639

See Changes: [Matt Sicker] Add fake site distribution to make maven-site-plugin happy [Matt Sicker] [LOG4J2-1802]: Migrate component sites to markdown -- [...truncated 327 lines...] cast to Object

Re: logging-log4j2 git commit: Normalize use of markdown headers

Dangling curly in download.md? Apache Log4j ${Log4jReleaseVersion} is signed by ${Log4jReleaseManager} (${Log4j Alternatively, you can verify Sent from my iPhone > On Jan 30, 2017, at 2:44, mattsic...@apache.org wrote: > > Apache Log4j ${Log4jReleaseVersion} is signed by ${Log4jReleaseManager}

Re: logging-log4j2 git commit: Normalize use of markdown headers

I see in the file: Apache Log4j ${Log4jReleaseVersion} is signed by ${Log4jReleaseManager} (${Log4jReleaseKey}) Email might've been buggy. On 29 January 2017 at 17:20, Remko Popma wrote: > Dangling curly in download.md? > > Apache Log4j ${Log4jReleaseVersion} is signed by ${Log4jReleaseManager

Re: logging-log4j2 git commit: Normalize use of markdown headers

Probably an artifact of the diffing format. Sorry about that. Sent from my iPhone > On Jan 30, 2017, at 8:42, Matt Sicker wrote: > > I see in the file: > > Apache Log4j ${Log4jReleaseVersion} is signed by ${Log4jReleaseManager} > (${Log4jReleaseKey}) > > Email might've been buggy. > >> On

[jira] (LOG4J2-1431) Simplify log4j system property naming scheme

Title: Message Title Gary Gregory commented on LOG4J2-1431