You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

download.xml 3.1KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. <?xml version="1.0" standalone="no"?>
  2. <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
  3. "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
  4. <document>
  5. <header>
  6. <title>FOP: Downloading A Distribution</title>
  7. </header>
  8. <body>
  9. <section id="dist-type">
  10. <title>Binary or Source?</title>
  11. <p>Most FOP users will want to download the latest binary distribution, which is ready to run "out of the box."
  12. However, a source distribution will be preferable if you fall into one of the following categories:</p>
  13. <ul>
  14. <li>You wish to modify FOP.</li>
  15. <li>You wish to use a version more recent than the latest release. For example, if you have read on the user mailing list that a bug has been fixed or a feature added that you are eager to try, you might download a source distribution from the CVS repository so that you don't have to wait for the next release.</li>
  16. <li>You wish to build a local copy of the API documentation (javadocs).</li>
  17. </ul>
  18. </section>
  19. <section id="binary">
  20. <title>Binary Download</title>
  21. <p>Binary distributions include "-bin" in their names, and can be downloaded from the <link href="http://xml.apache.org/dist/fop/">FOP Distribution</link> directory.
  22. </p>
  23. <note>We're in the process of moving the download location. Please download the
  24. latest release candidate from a
  25. <link href="http://www.apache.org/dyn/closer.cgi/xml/fop">mirror</link>.
  26. </note>
  27. </section>
  28. <section id="source">
  29. <title>Source Download</title>
  30. <p>You must first determine which of the two main development branches you wish to download, "maintenance" or "redesign".
  31. See <link href="dev/index.html">Development Introduction</link> for more details on the choices, and for the CVS tags to use when downloading the "maintenance" branch.</p>
  32. <p>There are three ways to obtain a source distribution. Please note that they are listed from least current to most current:</p>
  33. <ul>
  34. <li>Download a released version from the <link href="http://xml.apache.org/dist/fop/">FOP Distribution</link> directory. Source distributions include "-src" in their names. Please note that official releases currently are <em>only</em> made from the "maintenance" branch.</li>
  35. <li>Download a CVS snapshot from the cvs files <link href="http://xml.apache.org/from-cvs/xml-fop/">here</link>. These snapshots are built approximately every six hours, and have the GMT of their creation time embedded in their names. Please note that CVS snapshots are made only for the "redesign" branch.</li>
  36. <li>Download directly from the CVS repository.
  37. Anyone can do this using the <link href="http://xml.apache.org/cvs.html#AnonCVS">Anonymous CVS Server</link>. By default, the CVS code is up-to-the-minute, the same code that the developers are modifying. See the <link href="dev/tools.html#cvs">CVS section of Developer Tools</link> for more information on using CVS.</li>
  38. </ul>
  39. <p>With any source distribution, you will need to <link href="compiling.html">Build FOP</link> from the source files.</p>
  40. </section>
  41. </body>
  42. </document>
  43. <!-- Last Line of $RCSfile$ -->