[ xframe-Feature Requests-1176236 ] Add option to include raw XSDs in docs
"SourceForge.net" <[email protected]> Mon, 04 Apr 2005 02:29:30 -0700
| Newsgroups | gmane.text.xml.xframe.xsddoc |
|---|---|
| Message-ID | <[email protected]> |
Feature Requests item #1176236, was opened at 2005-04-04 11:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454394&aid=1176236&group_id=48863 Category: cross reference Group: xsddoc-0.7-beta Status: Open Priority: 5 Submitted By: Graham Leggett (minfrin) Assigned to: Nobody/Anonymous (nobody) Summary: Add option to include raw XSDs in docs Initial Comment: In the current doc generation process, hyperlinks are created pointing at the source XSDs used to generate the documentation. These hyperlinks assume however that the XSDs live at ../src/xsd relative to the docs root directory, when this is most often not the case. What in theory should happen is that the raw XSDs (or XSDs marked up with pretty printing of some kind) should be copied into the documentation tree. This makes it possible for the "maven site" WAR file to be generated, or just the documentation deployed, without including broken links to the source code which might not be there. At the very least, such a thing should be controlled by the xsddoc properties file. This should make the tool have a wider application than just local docs within the source tree. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454394&aid=1176236&group_id=48863 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click