I completely purged that mess from my memory. We need a solution that
just works and links to generated code are not "the solution"©. :-) When
I build log4net I get the following files:
* log4net.dll
* log4net.pdb
* log4net.xml
The latter is a parseable output of all the classes, methods,
properties, .. along with the fancy source documentation (authors,
remarks, ..). Is it possible to do a little XPATH and XSLT kung-fu to
get this (and/or pieces from it) into a "site.xml"-ish format that could
later be consumed by the maven site plugin?
On 2017-04-19 10:07, Stefan Bodewig wrote:
On 2017-04-18, Dominik Psenner wrote:
We probably should at least add a remark that points readers to the
SDK reference and avoid the double effort of maintaining the
documentation on the website too.
Likely, in particular since we've broken it twice during the 2.0.x
release series. Looks as if updating SHFB was bound to modify the file
names making deep links dangerous.
You had fixed the link inside config-examples back in October and later
releases have broken them again - this was easy to fix using
mod_rewrite.
I think I've found all other places and fixed them for the 2.0.8 site as
a short term fix.
Stefan
