Community
Participate
Working Groups
4.6 RC1. Currently we have to remind ourselves to touch the ISV doc, so that the latest Javadoc and extension point doc gets generated. Similar to the class file comparator we should have a comparator for ISV doc. The comparator could first check, whether there was a change in the repo and if not, compare the built doc bundle with the previous one. This comparison will have to ignore some differences, like the date in the generated Javadoc files.
If it helps, in the short run, remember the warnings about doc bundles are split out into their own file. Under "release engineering logs", near the bottom there is a link to "buildtimeComparatorDocBundle.log.txt". For example, http://download.eclipse.org/eclipse/downloads/drops4/I20160516-2000/buildlogs/comparatorlogs/buildtimeComparatorDocBundle.log.txt And, while the Tycho comparator began with the one in JDT (which is one that p2 uses) Tycho's version is a little different now. (such as, I doubt they allow for "extensions" as the platform's/p2 one did). And if someone is going to invest in improving the comparator, I'd suggest the issue with "TSA" signatures be fixed too. (I don't mean to be sounding negative, just reminding that the comparator is actually in Tycho).
