![apache ant user manual apache ant user manual](https://s3.manualzz.com/store/data/051578174_1-d30670c44f6654482b57f386cea4617f.png)
The FOP web site and documentation are generated using Apache Forrest.
#Apache ant user manual code
From the user's standpoint, the choice is either that they potentially have to look multiple places to get the information they need (which was rejected), or they have to filter out an occasional feature that is in code available subsequent to their release (which was accepted). Other approaches were considered, but all seemed to have significantly higher costs both to the users and the developers. For example, "Feature xyz is first available in Release n.nn.n". Features or other documentation that applies to unreleased code should be marked in such a way within the content that the user can determine whether and how it applies to the version they are using. The current thinking is that the website should reflect the current state of the repository code branch from which releases are made. The documentation and the product are in a constant state of change, and there is some difficulty in deciding what product state the website content should reflect. This is somewhat contrary to the principle above, which should be applied as a higher priority. To the extent possible, try to document a topic exactly once, in the place the user is most likely to look for it, then link to that from other locations as appropriate. To the extent possible, keep user content separate from developer content, primarily so the user doesn't have to filter out technical information. These principles should be changed if better or more practical ones are found, but they should probably be discussed and changed by common consent. These principles are not written in stone, but reflect the current philosophy, and are documented here primarily to help achieve consistency. The path to the documentation is src/documentation/content/xdocs.Īll documentation is maintained on the trunk.īasic documents are stored in XML files, and use DTDs provided by Apache Forrest. The remaining discussions on this page assume that the SVN repository is the starting place for processing. Updates should be committed to the repository, then the repository files are used to generate usable output. General InformationĪll raw documentation content is managed in the Apache™ FOP SVN repository. Do not follow this to make FOP documentation. Hope to see you there! ApacheCon Europe ¶Īpache™ FOP Development: Managing Documentation
![apache ant user manual apache ant user manual](https://image.slidesharecdn.com/ant-110512042724-phpapp01/95/ant-another-neat-tool-14-728.jpg)
Search Apache XML Graphics ¶ ApacheCon N.