: Done. Thanks for testing! I hate to be a buzz kill, but all this really does is replace the outdated javadoc generated index.html file with a new one that points at the subdirs we've created ... I don't see how this solves the root problem: Hudson doesn't delete the old files.... https://hudson.dev.java.net/issues/show_bug.cgi?id=1000
The "Publish JavaDoc" feature copies a configured path for javadocs into an existing "archive" directory -- any file that existed in a previous build of the javadocs and isn't in the current javadocs will still be there. All we've done is stop linking to the old flattened doc hierarchy, but any caches, bookmarks, or search engines linking to them will still find valid pages. In addition to my previous suggestion... http://www.gossamer-threads.com/lists/lucene/java-dev/70655#70655 ...another config option we could try is "Retain javadoc for each successful build". There is a warning that this causes it to take up more disk (because it keeps the javadocs for each build) but I *think* if we use that option, it will create a brand new javadoc directory for each build. (it looks like our uncompressed javadocs are about 5 times as big as our binary artifacts ... but we currently keep the last 30 builds which seem excessive. If we cut hte number of archived builds we keep to 5 we'd wind up using less disk) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
