Community
Participate
Working Groups
A couple of days back an integration build failed because of bad HTML markup in 1 file in jdt.doc.isv. See http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg19378.html. Build failure because of bad HTML markup is a bit extreme. Dani suggested the following two options 1) The help.buildHelpIndex Ant task from 'org.eclipse.help.base' gets changed, so that it no longer fails on invalid files. 2) We add error handling to the Ant file that builds the index, e.g. by using something like http://ant-contrib.sourceforge.net/tasks/tasks/trycatch.html. Is there already an error handling task? If so, we should simply use it when calling the help.buildHelpIndex Ant task.
Do we know which HTML error made the build fail? Note that HTML errors can also come from generated Javadocs. These are hard to find locally, since setup to generate the Javadocs locally is not trivial, so a local CHKPII run usually doesn't include them.
(In reply to comment #1) > Do we know which HTML error made the build fail? Yes. The following commit fixed the problem (a missing closing " for an href attribute) http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=17a33e21f64db9b8223663d78ab0feb0417eade7
It surprises me that this caused the build to fail. I thought we had these kind of doc problems all the time and they just manifest as chkpii problems in the test results.
(In reply to comment #3) > It surprises me that this caused the build to fail. I thought we had these kind > of doc problems all the time and they just manifest as chkpii problems in the > test results. Most of the time yes. I guess there are some special cases which cause the Ant task to fail.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
