Re: [log4cxx] Site / Documentation thoughts

2020-09-20 Thread Thorsten Schöning
Guten Tag Robert Middleton, am Sonntag, 20. September 2020 um 03:47 schrieben Sie: > Perhaps, although that does require doxygen to be installed. My > thought on that though > is that you only want to generate API docs on every commit if they are > clearly for > bleeding-edge uses; generally,

Re: [log4cxx] Site / Documentation thoughts

2020-09-20 Thread Thorsten Schöning
Guten Tag Matt Sicker, am Samstag, 19. September 2020 um 22:24 schrieben Sie: > The files that get published are now stored in git repos rather than > the svn repos. Subversion is used for artifacts only right now. This means the current process to publish the site for log4cxx is broken anyway

Re: [log4cxx] Site / Documentation thoughts

2020-09-19 Thread Robert Middleton
> > 1. Continue to utilize maven. This has the advantage of making the site > > consistent with the other log4___ sites. The disadvantage is that it > > is(currently) weird to update the site and has issues with releases. > > Another advantage is that Maven generates some parts automatically, >

Re: [log4cxx] Site / Documentation thoughts

2020-09-19 Thread Matt Sicker
The files that get published are now stored in git repos rather than the svn repos. Subversion is used for artifacts only right now. On Sat, 19 Sep 2020 at 10:00, Apache wrote: > > Changes made to subversion will have no effect. Logging services no longer > uses the ASF CMS. > > Ralph > > > On

Re: [log4cxx] Site / Documentation thoughts

2020-09-19 Thread Apache
Changes made to subversion will have no effect. Logging services no longer uses the ASF CMS. Ralph > On Sep 19, 2020, at 12:53 AM, Thorsten Schöning wrote: > > Guten Tag Ralph Goers, > am Samstag, 19. September 2020 um 04:16 schrieben Sie: > >> The main web site is built using JBake.

Re: [log4cxx] Site / Documentation thoughts

2020-09-19 Thread Thorsten Schöning
Guten Tag Robert Middleton, am Samstag, 19. September 2020 um 02:56 schrieben Sie: > 1. Continue to utilize maven. This has the advantage of making the site > consistent with the other log4___ sites. The disadvantage is that it > is(currently) weird to update the site and has issues with

Re: [log4cxx] Site / Documentation thoughts

2020-09-19 Thread Thorsten Schöning
Guten Tag Ralph Goers, am Samstag, 19. September 2020 um 04:16 schrieben Sie: > The main web site is built using JBake. Although it is Java based and still > uses Maven the command to build the site is just mvn install (although it > doesn’t actually do an install). All the web pages are

Re: [log4cxx] Site / Documentation thoughts

2020-09-18 Thread Matt Sicker
I’d say go for whichever format is most natural for the toolset and maintenance. I’m not tied to Maven site generation either. On Fri, Sep 18, 2020 at 21:17 Ralph Goers wrote: > The main web site is built using JBake. Although it is Java based and > still uses Maven the command to build the

Re: [log4cxx] Site / Documentation thoughts

2020-09-18 Thread Ralph Goers
The main web site is built using JBake. Although it is Java based and still uses Maven the command to build the site is just mvn install (although it doesn’t actually do an install). All the web pages are either Markdown or AsciiDoctor. I should also add that you don’t have to use Maven. You

[log4cxx] Site / Documentation thoughts

2020-09-18 Thread Robert Middleton
I've been working on smart pointer updates for log4cxx, and as part of that effort I would also like to improve the documentation to make sure that it is clear how to use the library. However, this brings up a question as to how we want to create the website. Currently, the main site is