> > 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, > like the overview for the lists, changes etc. One doesn't need to > maintain that manually too much, which would be the case when > switching. >
The mailing lists and download links are in my mind rather trivial to implement correctly, since they don't exactly change often. The changes still needs to be updated manually, so adding a new entry into a table doesn't seem like a big deal to me. > In any case one needs to have a look at the additional logic > implemented by MVN/ANT to decide if that is needed for the new site as > well. Some of that logic deals with SVN-specifics, but some is related > to updating versions numbers and stuff like that when I remember > correctly. So content-based changes would need some replacement. > The good news is that because cmake can also do text replacements, updating the version number only needs to happen in one place(the cmake files) instead of two or three(pom.xml, cmake files, autotools[if we still support autotools]). > You have worked on GitHub-actions, isn't that something which could be > used to update the API-docs automatically somehow? Those are pretty > different from the site anyway, the content of the latter is to be > maintained manually, while API-docs are designed to be generated > automatically on each commit in theory. 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, people should be using the documentation for the release that they are using. Anyway, I've done some conversion that you can see here: https://rm5248.com/log4cxx/apidocs/index.html I have not converted everything over yet(and there's still some formatting to fix), but at a minimum the main page, changelog, dependencies, and FAQ page should work. The usage page is there, but a lot of the formatting is missing at the moment. The page links on the left can be reordered somehow and given drop-downs like the entries for 'Classes' to match closer with maven. -Robert Middleton
