Generated code or generated documentation shouldn't be on the VCS (subversion), right?
Christian, what is the best practice here in ASF? There should be a script that updates the site with the latest documentation, and this should be done by the Promotion step when we decide a new version may be delivered. This is the reason of the automation task using "nightly builds", using the #jenkins ASF etc. What is your opinion on that? Should we consider from now on, as rule of thumb, that NEVER we should put generated code on the VCS? Regards, Alex On Jan 7, 2014 1:38 PM, "Thorsten Schöning" <tschoen...@am-soft.de> wrote: > Hello, > > the documentation about how to use log4cxx contains some links to > classes in the apidocs folder, like the following: > > > apidocs/classlog4cxx_1_1Logger.html#e3 > > Those links changed with the newer versions of doxygen to something > like the following: > > > apidocs/classlog4cxx_1_1_logger.html#afc0e4d99cab7c38a2851d41e6edc1dee > > The file name itself changed, 1_1Logger vs. 1_1_logger, and the anchor > is a md5 sum of the signature of the linked method, in this example > log4cxx::Logger::getRootLogger got linked. Whenever the signature of > the method changes, the anchor gets invalid until the link is updated > to the new id. > > Does anyone has any experience with Doxygen regarding this kind of > "issue" or any clever idea how to deal with this? I may tent to don't > use ids in the links at all and hope that file names won't change that > often. > > 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 > >
