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

See

[jira] [Closed] (LOG4J2-1954) Configurations with multiple root loggers should fail loudly

[ https://issues.apache.org/jira/browse/LOG4J2-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1954. --- Resolution: Fixed Fix Version/s: 2.9 Fixed in master. > Configurations with multiple root log

[jira] [Commented] (LOG4J2-1954) Configurations with multiple root loggers should fail loudly

[ https://issues.apache.org/jira/browse/LOG4J2-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069535#comment-16069535 ] ASF subversion and git services commented on LOG4J2-1954: - Commit

[jira] [Assigned] (LOG4J2-1954) Configurations with multiple root loggers should fail loudly

[ https://issues.apache.org/jira/browse/LOG4J2-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1954: --- Assignee: Remko Popma > Configurations with multiple root loggers should fail loudly > -

Jenkins build became unstable: Log4j 2.x #2853

See

[jira] [Commented] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069322#comment-16069322 ] ASF subversion and git services commented on LOG4J2-1960: - Commit

[jira] [Updated] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1960: - Description: Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1. > Update ZeroMQ's JeroMQ from 0.4.0 to 0

[jira] [Closed] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1960. Resolution: Fixed Fixed issue title and description. Thank you Matt, > Update ZeroMQ's JeroMQ from

[jira] [Updated] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1960: - Summary: Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1 (was: Update ZeroMQ's JeroMQ from 0.4.1 to 0

[jira] [Reopened] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1.

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1960: -- > Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1. > --- > >

[jira] [Updated] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1960: - Description: (was: Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1.) > Update ZeroMQ's JeroMQ from

[jira] [Closed] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1960. Resolution: Fixed > Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1 > --

[jira] [Reopened] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1960: -- > Update ZeroMQ's JeroMQ from 0.4.0 to 0.4.1 > -- > >

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069140#comment-16069140 ] Gary Gregory commented on LOG4J2-1934: -- I did and I will rewrite the JMS appender.

Re: Release notes

It's a markdown file, btw, so it looks nicer on GitHub and makes it easier to copy/paste for the release email (get links and such that way). It's included in the distribution zip for old-school users as well. On 29 June 2017 at 15:16, Ralph Goers wrote: > The RELEASE-NOTES.md is generated from

[jira] [Commented] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1.

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069056#comment-16069056 ] Matt Sicker commented on LOG4J2-1960: - >From 0.4.1 to 0.4.1? > Update ZeroMQ's JeroM

[jira] [Commented] (LOG4J2-1958) Deprecate SerializedLayout and remove it as default

[ https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069028#comment-16069028 ] ASF subversion and git services commented on LOG4J2-1958: - Commit

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

See

Jenkins build is unstable: Log4j 2.x #2847

See

[jira] [Closed] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1.

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1960. Resolution: Fixed Fix Version/s: 2.9 In Git master. > Update ZeroMQ's JeroMQ from 0.4.1 to

[jira] [Commented] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1.

[ https://issues.apache.org/jira/browse/LOG4J2-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068955#comment-16068955 ] ASF subversion and git services commented on LOG4J2-1960: - Commit

[jira] [Created] (LOG4J2-1960) Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1.

Gary Gregory created LOG4J2-1960: Summary: Update ZeroMQ's JeroMQ from 0.4.1 to 0.4.1. Key: LOG4J2-1960 URL: https://issues.apache.org/jira/browse/LOG4J2-1960 Project: Log4j 2 Issue Type: Tas

Re: Release notes

The RELEASE-NOTES.md is generated from the announcement.vm and changes.xml. It is in git so a) it will appear in GitHub, b) it is in the root of both the source and binary zips. The source zip is just a copy of the source directory at the time of the build so it has to be committed to git for th

Build failed in Jenkins: Log4j 2.x #2846

See Changes: [mikael] LOG4J2-1958 Deprecate SerializedLayout and remove it as default [mikael] LOG4J2-1958 Fix tests [mikael] LOG4J2-1958 Specify version when SerializedLayout is deprecated [mikael] LOG4J2-1958 Lin

Re: Release notes

What about the /RELEASE-NOTES.md file? Is it generated? Then why is it in Git? On 2017-06-29 21:52, Ralph Goers wrote: I should also add that the release manager will be the “final” editor of it as part of the release and may make changes, deletions or corrections. Ralph On Jun 29, 2017, at

Re: Release notes

I should also add that the release manager will be the “final” editor of it as part of the release and may make changes, deletions or corrections. Ralph > On Jun 29, 2017, at 12:50 PM, Ralph Goers wrote: > > I wouldn’t use the word “appended”. announcement.vm is free-form text that > describe

Re: Release notes

I wouldn’t use the word “appended”. announcement.vm is free-form text that describes the release. It should be edited as needed. Most enhancements and fixes don’t need to be called out there. Ralph > On Jun 29, 2017, at 12:14 PM, Gary Gregory wrote: > > Just documenting which file to update a

Re: Release notes

Just documenting which file to update and that it gets appended... On Jun 29, 2017 12:11 PM, "Ralph Goers" wrote: > Updating the release notes is already a step in the release process. Are > you talking about a different wiki page? > > Ralph > > > On Jun 29, 2017, at 10:33 AM, Gary Gregory > wr

Re: Release notes

Updating the release notes is already a step in the release process. Are you talking about a different wiki page? Ralph > On Jun 29, 2017, at 10:33 AM, Gary Gregory wrote: > > Another step in the wiki? > > Gary > > On Jun 29, 2017 08:42, "Mikael Ståldal" wrote: > >> OK, I just started the

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068785#comment-16068785 ] Ralph Goers commented on LOG4J2-1934: - As I suggested before, take a look at how the

[jira] [Commented] (LOG4J2-1959) Disable DTD processing in XML configuration files

[ https://issues.apache.org/jira/browse/LOG4J2-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068709#comment-16068709 ] Mikael Ståldal commented on LOG4J2-1959: Lower privileged users are not supposed

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068686#comment-16068686 ] Gary Gregory commented on LOG4J2-1934: -- Hi Ralph, Thank you for the review. My mot

Poms and versions

Hi All, I keep on seeing patches with version 2.8.3 in the comments and @since tags. This is understandable since ours Poms use version 2.8.3-SNAPSHOT. I plan on changing Poms to 2.9-SNAPSHOT to avoid this noise. Gary

Re: Release notes

Another step in the wiki? Gary On Jun 29, 2017 08:42, "Mikael Ståldal" wrote: > OK, I just started the good practice. > > > On 2017-06-29 16:53, Ralph Goers wrote: > >> I edit src/site/announcment.vm as required before releases to call out >> anything special. It would be good practice to edit

[jira] [Commented] (LOG4J2-1959) Disable DTD processing in XML configuration files

[ https://issues.apache.org/jira/browse/LOG4J2-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068627#comment-16068627 ] Brian Martin commented on LOG4J2-1959: -- Can you clarify the potential attack vector?

[jira] [Comment Edited] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068545#comment-16068545 ] Ralph Goers edited comment on LOG4J2-1934 at 6/29/17 4:16 PM: -

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068545#comment-16068545 ] Ralph Goers commented on LOG4J2-1934: - I just took a look at the commit and I do NOT

[jira] [Resolved] (LOG4J2-1958) Deprecate SerializedLayout and remove it as default

[ https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1958. Resolution: Fixed In Git master. > Deprecate SerializedLayout and remove it as default > -

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068508#comment-16068508 ] ASF subversion and git services commented on LOG4J2-1934: - Commit

Re: Release notes

OK, I just started the good practice. On 2017-06-29 16:53, Ralph Goers wrote: I edit src/site/announcment.vm as required before releases to call out anything special. It would be good practice to edit during development so that I don’t forget things. The changes.xml content gets appended to t

Re: Release notes

I edit src/site/announcment.vm as required before releases to call out anything special. It would be good practice to edit during development so that I don’t forget things. The changes.xml content gets appended to the announcement text. Ralph > On Jun 29, 2017, at 6:02 AM, Mikael Ståldal wrote

Re: Release notes

Yes, but in this case I want something more which cannot be placed in changes.xml. On 2017-06-29 14:37, Remko Popma wrote: Release Notes = changes.xml, no? (Shameless plug) Every java main() method deserves http://picocli.info On Jun 29, 2017, at 19:48, Mikael Ståldal wrote: Do we have any

Re: Release notes

Release Notes = changes.xml, no? (Shameless plug) Every java main() method deserves http://picocli.info > On Jun 29, 2017, at 19:48, Mikael Ståldal wrote: > > Do we have any place to prepare release notes for an upcoming release, before > actually making the release? > > Removing SerializedLa

Release notes

Do we have any place to prepare release notes for an upcoming release, before actually making the release? Removing SerializedLayout as default warrants a mentioning in the release notes for the 2.9 release, since it is a breaking change.