1 <?xml version="1.0" encoding="UTF-8"?>
3 <sect1 id="zend.tool.framework.system-providers">
4 <title>Shipped System Providers</title>
7 In addition to the more useful project based providers that come shipped
8 with <classname>Zend_Tool_Project</classname>, there are also some more basic, but
9 interesting providers that come built into
10 <classname>Zend_Tool_Framework</classname>. Some of these exist for the purpose
11 of providing a means via the command line to extract information, such
12 as the version, while others are intended to aid the developer when
13 creating additional providers.
16 <sect2 id="zend.tool.framework.system-providers.version">
17 <title>The Version Provider</title>
20 The Version provider is included so that you may determine which
21 version of the framework that the <command>zf</command> or
22 <classname>Zend_Tool</classname> is currently set to work with.
26 Through the command line, simply run <command>zf show version</command>.
30 <sect2 id="zend.tool.framework.system-providers.manifest">
31 <title>The Manifest Provider</title>
34 The Manifest provider is included so that you may determine what
35 kind of "manifest" information is available during the
36 <classname>Zend_Tool</classname> runtime. Manifest data is information that
37 is attached to specific objects during <classname>Zend_Tool</classname>'s
38 runtime. Inside the manifest you will find the console specific
39 namings that you are expected to use when calling certain commands.
40 Data found in the manifest can be used by any provider or client on
45 Through the command line, simply run <command>zf show manifest</command>.