| Summary: | o.e.d.doc.isv doc content for Extension Point Schema Definitions get out-of-date | ||
|---|---|---|---|
| Product: | [Tools] Data Tools | Reporter: | Linda Chan <lchan> |
| Component: | releng | Assignee: | Xiaoying Gu <bluesoldier> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bluesoldier |
| Version: | 1.9 | ||
| Target Milestone: | 1.9.2 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Linda Chan
This will need further investigation on whether it is feasible for the build process to auto generate the html doc files from the schema/*.exsd files. In the mean time, I have checked in updates to the static html files kept in o.e.d.doc.isv for the o.e.d.connectivity.oda* and o.e.d.connectivity extension points. Tagged with v201109290731. similar bug in platform team: https://bugs.eclipse.org/bugs/show_bug.cgi?id=35145 Until there is an automated solution, can we use a custom script to generate the schema doc? So at least any updates to existing xsd will get an updated doc generated. And committers that introduce a new xsd will need to manually add an entry in the custom script. CreateSchemaReference target has been added to BuildDocISV.xml under doc.isv plugin. If a new xsd file is introduced in a plugin for the first time, committer should update the BuildDocISV.xml manually. If a new schema is introduced, plugins/org.eclipse.datatools.doc.isv/tocreference.xml file need to be updated manually with a new topic link for added schema. |