Guten Tag Robert Middleton, am Montag, 3. August 2020 um 02:17 schrieben Sie:
> I'd like to propose some new features/updates for log4cxx, if there's > interest. Things mostly read good and interesting to me. Even though I would suffer myself a lot most likely, as my currently used compiler/IDE is mostly not even compatible with C++11. :-) > A number of these are rather large changes, so it probably > doesn't make sense to work on them until there's a known-good release, as > they would likely break both API and ABI compatibility. Does it really matter much if things are broken now vs. with 0.12.0 or alike? Backwards compatibility was somewhat broken already when changing how the macros are implemented, when returning new LevelPtrs to fix threading-issues and with introducing CMAKE in favor of building with Maven+ANT. We might not need to care too much in favor of implementing changes users benefit from. > 3. Removal of maven for site generation.[...] The good thing about the current approach is that Maven does some things automatically, which would otherwise not be available or need to be maintained manually. Think of the changes-report, providing mailing list info, linking to issue tracker, even dependencies could be enhanced. Additionally, ANT is used to simply automate somewhat cross-platform things which would need to be implemented otherwise. Maven shouldn't be used for building anymore and not using it for releasing would simply require another implementation. Even though things seemed to have somewhat worked for you. So this doesn't read too important to me and things can be changed step-by-step: Change usage of ANT, using Doxygen at least as PoC for some sites can simply be added as Doxygen is already needed anyway etc. > 4. ABI compatibility.[...] In general I prefer more straightforward class declarations and wouldn't care too much about changing each and every class to pimpl. > 2. Remove the autotools build[...]Is > there a particular reason to keep it around still? AFAIK only backwards compatibility. > 3. Support for log4j2-style XML/JSON/YAML documents.[...] For the time being, it might be far easier to document more on our own instead. Might be a good chance to add Doxygen-based content like you proposed. > Going through the currently open issues in JIRA, there's also a large > number that are either so old that they don't make much sense, or may have > been fixed already. Would it make sense to go through them at some point? > That's probably not something that I can do alone, but I can help to go > through them. Would be enough already if you would go through them and provide a second opinion about which of those could easily be closed. I would close ideas like APR database layer, CI-related stuff etc. most likely. Additionally some very old 0.9.7-related issues. But that keeps lots of other errors and improvements like new appenders. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
