Re: Review Request: LOG4J2-3628 Migrate from maven-changes-plugin to a merge-conflict-free Markdown-based solution

2022-11-08 Thread Matt Sicker
This is why I’ve suggested accepting bug reports via email in addition to GitHub. Any bug tracker we use which isn’t hosted by Apache will likely have similar issues. > On Nov 7, 2022, at 8:58 PM, Gary Gregory wrote: > > Just FYI, > > There is a release note discussion going on on the Maven l

Re: Review Request: LOG4J2-3628 Migrate from maven-changes-plugin to a merge-conflict-free Markdown-based solution

2022-11-08 Thread Carter Kozak
On Tue, Nov 8, 2022, at 14:28, Matt Sicker wrote: > Any bug tracker we use which isn’t hosted by Apache will likely have similar > issues. The Apache Jira instance has the same issue at this point, even more broadly. I agree that the mailing list is a reasonable option for folks to report issues

Re: Review Request: LOG4J2-3628 Migrate from maven-changes-plugin to a merge-conflict-free Markdown-based solution

2022-11-08 Thread Gary Gregory
I do like all the details in the Jira ticket! :-) Gary On Mon, Nov 7, 2022, 16:03 Volkan Yazıcı wrote: > In the context of migrating away from JIRA to GitHub Issues, I want to > replace the current maven-changes-plugin setup with a merge-conflict-free > Markdown-based solution. I have elaborate

[log4cxx] C++ Version

2022-11-08 Thread Robert Middleton
The current version of next_stable fails when compiled in C++11 mode due to std::make_unique not being in that version. This is pretty easy to fix(Herb Sutter has an implementation of this for C++11 which seems to be the same as GCC's: https://herbsutter.com/gotw/_102/) I see three options here: