You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-svn@forrest.apache.org by cr...@apache.org on 2007/04/11 04:03:34 UTC
svn commit: r527368 [4/6] - in
/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo:
./ docs/developer/useCases/ docs/user/useCases/ images/ skin/ skin/images/
svn-log/ useCases/
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/docs/user/useCases/useCaseFeatures.source.xml
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/docs/user/useCases/useCaseFeatures.source.xml?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/docs/user/useCases/useCaseFeatures.source.xml (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/docs/user/useCases/useCaseFeatures.source.xml Tue Apr 10 19:03:32 2007
@@ -15,24 +15,27 @@
limitations under the License.
--><useCases>
<title>Uses Cases for the Use Case management features of org.apache.forrest.plugin.input.projectInfo</title>
-
<useCase>
<title>Write Use Case Documentation</title>
<description>
- <p>Write semi-structured use case documents so that they can be reused in a variety of ways.
- This use case describews a process for writing such documents. This document is derived from
- such a <a href="useCaseFeatures.source.xml">source document</a>.</p>
-
+ <p>
+ Write semi-structured use case documents so that they can be reused in a
+ variety of ways. This use case describews a process for writing such
+ documents. This document is derived from such a
+ <a href="useCaseFeatures.source.xml">source document</a>.
+ </p>
<section>
<title>Justification</title>
-
- <p>A use case describes a unit of work. It is typically used in the design
- stages of a software project. It is very useful for describing what an applicaiton must
- do and what patchs through the system can be taken.</p>
-
- <p>By bringing this information together in a semi-structured document we can use it in many
- different ways. For example:</p>
-
+ <p>
+ A use case describes a unit of work. It is typically used in the
+ design stages of a software project. It is very useful for describing
+ what an applicaiton must do and what patchs through the system can be
+ taken.
+ </p>
+ <p>
+ By bringing this information together in a semi-structured document we
+ can use it in many different ways. For example:
+ </p>
<ul>
<li>Requirements Documentation</li>
<li>Developer Documentation</li>
@@ -41,181 +44,198 @@
<li>Task Lists</li>
</ul>
</section>
-
</description>
-
<steps>
<step>
<title>Create/open a Use Case file</title>
- <description>In your favourite XML editor either create a new file
- or open an existing use case file. The default location of these files
- within a Forrest content object is <code>/content/documentation/useCases/**.xml</code>
+ <description>
+ In your favourite XML editor either create a new file or open an
+ existing use case file. The default location of these files within a
+ Forrest content object is
+ <code>/content/documentation/useCases/**.xml</code>
</description>
<result>You have either a blank use case document or an existing one ready for editing.</result>
-
- <fixme priority="Medium">Create a DTD for use case descriptions.</fixme>
- <fixme priority="High">Aggregate all documents in the useCases directory to provide
- ne large document describing all use cases.</fixme>
+ <fixme priority="Medium">
+ Create a DTD for use case descriptions.
+ </fixme>
+ <fixme priority="High">
+ Aggregate all documents in the useCases directory to provide ne large
+ document describing all use cases.
+ </fixme>
</step>
-
<step>
<title>Create a new use case</title>
<description>
- <p>A use case is enclosed within a <code>useCase</code> element.
- Each use case should be given a brief <code>title</code> to describe it.</p>
-
+ <p>
+ A use case is enclosed within a <code>useCase</code> element. Each
+ use case should be given a brief <code>title</code> to describe it.
+ </p>
</description>
-
<result>You have the container for your new use case.</result>
</step>
-
- <step>
- <title>Describe the overall objective of the use case</title>
- <description>
- <p>Each use case should be described in terms of:</p>
- <ul>
- <li>The objective</li>
- <li>The expected results</li>
- <li>The justification</li>
- </ul>
- <p>This information should be placed in the <code>description</code> element
- of your use case. This node allows any XDoc markup and therefore you are
- reasonably free to use whatever formatting or images are needed to convey the
- important details most efficiently.</p>
- </description>
-
- <result>You have a use case that is described sufficiently well for an average user of the end system
+ <step>
+ <title>Describe the overall objective of the use case</title>
+ <description>
+ <p>
+ Each use case should be described in terms of:
+ </p>
+ <ul>
+ <li>The objective</li>
+ <li>The expected results</li>
+ <li>The justification</li>
+ </ul>
+ <p>
+ This information should be placed in the <code>description</code>
+ element of your use case. This node allows any XDoc markup and
+ therefore you are reasonably free to use whatever formatting or
+ images are needed to convey the important details most efficiently.
+ </p>
+ </description>
+ <result>You have a use case that is described sufficiently well for an average user of the end system
to understand its purpose.</result>
- </step>
-
- <step>
- <title>Define each step in the Use Case</title>
- <description>
- <p>Each use case will be subdivided into one or more steps that must be carried out
- in order to complete the task. Each of these steps is defined within a <code>step</code>
- element which are chilren of a <code>steps</code> element.</p>
- </description>
- </step>
-
- <step>
- <title>Descripbe the step</title>
- <description>
- <p>Each step has a title and a description. The description should provide enough information
- for a user to complete the task and for a developer to implement support for the user in that
- task.</p>
-
- <p>In addition each step can be described as required or optional. By default a step is assumed
- be required. To set it to optional add a <code>required="false"</code> attribute to the
- <code>step</code> element.</p>
- </description>
-
- <result>A user will be able to follow instructions on how to carry out the step.</result>
- </step>
+ </step>
+ <step>
+ <title>Define each step in the Use Case</title>
+ <description>
+ <p>
+ Each use case will be subdivided into one or more steps that must be
+ carried out in order to complete the task. Each of these steps is
+ defined within a <code>step</code> element which are chilren of a
+ <code>steps</code> element.
+ </p>
+ </description>
+ </step>
+ <step>
+ <title>Descripbe the step</title>
+ <description>
+ <p>
+ Each step has a title and a description. The description should
+ provide enough information for a user to complete the task and for a
+ developer to implement support for the user in that task.
+ </p>
- <step>
- <title>Describe the expected results</title>
- <description>
- <p>Provide, within a <code>result</code> a brief description of the expected results from
- this step. This should summarise what state the application will be in once this use case
- has been performed.</p>
- </description>
- <result>You will have provided enough information to allow developers to test the functionality and
+ <p>
+ In addition each step can be described as required or optional. By
+ default a step is assumed be required. To set it to optional add a
+ <code>required="false"</code> attribute to the <code>step</code>
+ element.
+ </p>
+ </description>
+ <result>A user will be able to follow instructions on how to carry out the step.</result>
+ </step>
+ <step>
+ <title>Describe the expected results</title>
+ <description>
+ <p>
+ Provide, within a <code>result</code> a brief description of the
+ expected results from this step. This should summarise what state
+ the application will be in once this use case has been performed.
+ </p>
+ </description>
+ <result>You will have provided enough information to allow developers to test the functionality and
users to identify when a step has been succesfully completed.</result>
- </step>
-
- <step required="false">
- <title>Add "fixme" notes</title>
- <description>
- <p>A fixme note is enclosed within a <code>fixme</code> element. It describes something that
- remains to be done within this step. Each fixme has a priority attribute which can take one of
- of the followin values:</p>
-
- <ul>
- <li>Enhancement - a nice to have ehancment that may or may not be implemented.</li>
- <li>Low - this is considered an important addition to the use case, but everything works without it.</li>
- <li>High - this is an important addition. Everything works without it, but having this implmeneted would
+ </step>
+ <step required="false">
+ <title>Add "fixme" notes</title>
+ <description>
+ <p>
+ A fixme note is enclosed within a <code>fixme</code> element. It
+ describes something that remains to be done within this step. Each
+ fixme has a priority attribute which can take one of of the followin
+ values:
+ </p>
+ <ul>
+ <li>Enhancement - a nice to have ehancment that may or may not be implemented.</li>
+ <li>Low - this is considered an important addition to the use case, but everything works without it.</li>
+ <li>High - this is an important addition. Everything works without it, but having this implmeneted would
improve the application considerably.</li>
- <li>Major - this is nor preventing work that utilises the use case, but it is considered a requirement
+ <li>Major - this is nor preventing work that utilises the use case, but it is considered a requirement
for the next release since it adds key functionlaity.</li>
- <li>Blocker - this is preventing the correct operation of this use case and must be implmeneted ASAP</li>
- </ul>
-
- <p>Although this step is optional, it is good practice to allways add a
- <code><fixme priority="blocker">Not yet implemented</fixme></code>
- element to all new steps. This is becuase these nodes will be used to build a
- functionality matrix later on.</p>
- </description>
-
- <result>Users will be able to understand to what degree a step is implemented and developers will be able to
+ <li>Blocker - this is preventing the correct operation of this use case and must be implmeneted ASAP</li>
+ </ul>
+ <p>
+ Although this step is optional, it is good practice to allways add a
+ <code><fixme priority="blocker">Not yet
+ implemented</fixme></code> element to all new steps. This is
+ becuase these nodes will be used to build a functionality matrix
+ later on.
+ </p>
+ </description>
+ <result>Users will be able to understand to what degree a step is implemented and developers will be able to
see what remains to be done.</result>
-
- <fixme priority="enhancement">All fixmes to link to an issue tracker entry</fixme>
- </step>
-
- <step required="false">
- <title>Add alternatives</title>
- <description>
- <p>Sometimes there will be alternative paths through each step. These can be described in an
- <code>alternatives</code> element that allows free-form XDoc content. However, please be
- careful, if an alternative is more than a simple variation you may want to consider a
- whole new use case for the alternative.</p>
- </description>
-
- <result>Minor variations in the path through a use case will be documented for your users.</result>
- </step>
-
- <step required="false">
- <title>Write Implementation Notes</title>
- <description>
- <p>Developer implementation notes for each of the steps should be added either when writing the
- initial use case or later during the development phases of the use case. These notes are for technical readers
- and are intended to help those who come after the initial author to get a starting point when inspecting how
- a feature is implemented. It is not intended that these notes will contain full implementation details, only an
- overview should be provided.</p>
- </description>
-
- <result>A technical reader will be able to gain a baisc understanding of how each step is implemented in the
+ <fixme priority="enhancement">
+ All fixmes to link to an issue tracker entry
+ </fixme>
+ </step>
+ <step required="false">
+ <title>Add alternatives</title>
+ <description>
+ <p>
+ Sometimes there will be alternative paths through each step. These
+ can be described in an <code>alternatives</code> element that allows
+ free-form XDoc content. However, please be careful, if an
+ alternative is more than a simple variation you may want to consider
+ a whole new use case for the alternative.
+ </p>
+ </description>
+ <result>Minor variations in the path through a use case will be documented for your users.</result>
+ </step>
+ <step required="false">
+ <title>Write Implementation Notes</title>
+ <description>
+ <p>
+ Developer implementation notes for each of the steps should be added
+ either when writing the initial use case or later during the
+ development phases of the use case. These notes are for technical
+ readers and are intended to help those who come after the initial
+ author to get a starting point when inspecting how a feature is
+ implemented. It is not intended that these notes will contain full
+ implementation details, only an overview should be provided.
+ </p>
+ </description>
+ <result>A technical reader will be able to gain a baisc understanding of how each step is implemented in the
application.</result>
- </step>
+ </step>
</steps>
</useCase>
-
<useCase status="In Progress" owner="open">
<title>Generate Use Case Documentation for Developers</title>
-
<description>
- <p>Generate a complete list of all use cases for a project in a format useful to
- developers of the application. This list is to include:</p>
-
+ <p>
+ Generate a complete list of all use cases for a project in a format
+ useful to developers of the application. This list is to include:
+ </p>
<ul>
<li>a description of the use case</li>
<li>a summary of each of the steps involved</li>
<li>full details of each of the steps</li>
<li>a description of the expected outcome of each step</li>
<li>details of common alternatives in each step</li>
- <li>implementation notes for each step</li>
+ <li>implementation notes for each step</li>
</ul>
-
<section>
<title>Justification</title>
- <p>A use case describes a unit of work. It is typically used in the design
- stages of a software project, however, they can often be useful in creating
- user documentaiton. Especially when they describe user interface functionality.</p>
-
- <warning>Unfortunately this use case document does not currently cover all functions
- of the plugin since this functionlaity was added after many other features. Whilst you
- are exploring this feature, why not add a use case to the plugin and submit a patch
- so that those coming after you can enjoy more complete documentation.</warning>
+ <p>
+ A use case describes a unit of work. It is typically used in the
+ design stages of a software project, however, they can often be useful
+ in creating user documentaiton. Especially when they describe user
+ interface functionality.
+ </p>
+ <warning>
+ Unfortunately this use case document does not currently cover all
+ functions of the plugin since this functionlaity was added after many
+ other features. Whilst you are exploring this feature, why not add a
+ use case to the plugin and submit a patch so that those coming after
+ you can enjoy more complete documentation.
+ </warning>
</section>
</description>
-
<steps>
<step>
<title>Make HTTP request</title>
<description>
<p>
- Request
- http://localhost:8888/docs/developer/useCases.xml
+ Request http://localhost:8888/docs/developer/useCases.xml
</p>
</description>
<result>
@@ -223,38 +243,48 @@
An XDoc is created that describes the use cases
</p>
</result>
-
- <fixme priority="High">Make the summary optional - already added
- $includeImplementationNotes parameter to stylesheet. Need to pass value form sitemap.</fixme>
-
+ <fixme priority="High">
+ Make the summary optional - already added $includeImplementationNotes
+ parameter to stylesheet. Need to pass value form sitemap.
+ </fixme>
<alternatives>
- <p>Depending on what plugins are available within your running instance of Forrest you will
- be able to request different output formats as per the usual Forrest usage. For example requesting
- a http://localhost:8888/docs/developer/useCases.html will generate the HTML document, whilst
- http://localhost:8888/docs/developer/useCases.pdf will generate the PDF document (as long
- as you have the relevant plugins installed).</p>
+ <p>
+ Depending on what plugins are available within your running instance
+ of Forrest you will be able to request different output formats as
+ per the usual Forrest usage. For example requesting a
+ http://localhost:8888/docs/developer/useCases.html will generate the
+ HTML document, whilst
+ http://localhost:8888/docs/developer/useCases.pdf will generate the
+ PDF document (as long as you have the relevant plugins installed).
+ </p>
</alternatives>
-
<implementation>
<description>
- <p>The source document for use cases is, by default, called <code>useCases.xml</code> and is
- located in the root of the projects xdocs directory.</p>
-
- <p>The URL space <code>docs/**/useCases.xml</code> is reserved for the projectInfo plugin. A request to
- /docs/developer/useCases.xml results in the useCases.xml file being translated into an XDoc as per
- the usual forrest processing. See the input.xmap file fo this plugin,</p>
+ <p>
+ The source document for use cases is, by default, called
+ <code>useCases.xml</code> and is located in the root of the
+ projects xdocs directory.
+ </p>
+
+ <p>
+ The URL space <code>docs/**/useCases.xml</code> is reserved for
+ the projectInfo plugin. A request to /docs/developer/useCases.xml
+ results in the useCases.xml file being translated into an XDoc as
+ per the usual forrest processing. See the input.xmap file fo this
+ plugin,
+ </p>
</description>
</implementation>
</step>
</steps>
</useCase>
-
<useCase status="In Progress" owner="open">
<title>Generate Use Case Documentation for Users</title>
-
<description>
- <p>Generate a complete list of all use cases for a project. This list is to include:</p>
-
+ <p>
+ Generate a complete list of all use cases for a project. This list is to
+ include:
+ </p>
<ul>
<li>a description of the use case</li>
<li>a summary of each of the steps involved</li>
@@ -262,27 +292,29 @@
<li>a description of the expected outcome of each step</li>
<li>details of common alternatives in each step</li>
</ul>
-
<section>
<title>Justification</title>
- <p>A use case describes a unit of work. It is typically used in the design
- stages of a software project, however, they can often be useful in creating
- user documentaiton. Especially when they describe user interface functionality.</p>
-
- <warning>Unfortunately the use case document does not currently cover all functions
- of the plugin since this functionlaity was added after many other features. Whilst you
- are exploring this feature, why not add a use case to the plugin and submit a patch
- so that those coming after you can enjoy more complete documentation.</warning>
+ <p>
+ A use case describes a unit of work. It is typically used in the
+ design stages of a software project, however, they can often be useful
+ in creating user documentaiton. Especially when they describe user
+ interface functionality.
+ </p>
+ <warning>
+ Unfortunately the use case document does not currently cover all
+ functions of the plugin since this functionlaity was added after many
+ other features. Whilst you are exploring this feature, why not add a
+ use case to the plugin and submit a patch so that those coming after
+ you can enjoy more complete documentation.
+ </warning>
</section>
</description>
-
<steps>
<step>
<title>Make HTTP request</title>
<description>
<p>
- Request
- http://localhost:8888/docs/user/useCases.xml
+ Request http://localhost:8888/docs/user/useCases.xml
</p>
</description>
<result>
@@ -290,46 +322,60 @@
An XDoc is created that describes the use cases
</p>
</result>
-
- <fixme priority="High">Enable the retrieval of a specific use case rather than all at once.</fixme>
- <fixme priority="Low">Make the summary optional - there is a switch in the XSL for this, just need to pass a property
- from the XMAP</fixme>
-
+ <fixme priority="High">
+ Enable the retrieval of a specific use case rather than all at once.
+ </fixme>
+ <fixme priority="Low">
+ Make the summary optional - there is a switch in the XSL for this,
+ just need to pass a property from the XMAP
+ </fixme>
<alternatives>
- <p>Depending on what plugins are available within your running instance of Forrest you will
- be able to request different output formats as per the usual Forrest usage. For example requesting
- a http://localhost:8888/docs/user/useCases.html will generate the HTML document, whilst
- http://localhost:8888/docs/user/useCases.pdf will generate the PDF document (as long
- as you have the relevant plugins installed).</p>
+ <p>
+ Depending on what plugins are available within your running instance
+ of Forrest you will be able to request different output formats as
+ per the usual Forrest usage. For example requesting a
+ http://localhost:8888/docs/user/useCases.html will generate the HTML
+ document, whilst http://localhost:8888/docs/user/useCases.pdf will
+ generate the PDF document (as long as you have the relevant plugins
+ installed).
+ </p>
</alternatives>
-
<implementation>
<description>
- <p>The source document for use cases is, by default, called <code>useCases.xml</code> and is
- located in the root of the projects xdocs directory.</p>
-
- <p>The URL space <code>docs/**/useCases.xml</code> is reserved for the projectInfo plugin. A request to
- /docs/user/useCases.xml results in the useCases.xml file being translated into an XDoc as per
- the usual forrest processing, see input.xmap for more details.</p>
+ <p>
+ The source document for use cases is, by default, called
+ <code>useCases.xml</code> and is located in the root of the
+ projects xdocs directory.
+ </p>
+
+ <p>
+ The URL space <code>docs/**/useCases.xml</code> is reserved for
+ the projectInfo plugin. A request to /docs/user/useCases.xml
+ results in the useCases.xml file being translated into an XDoc as
+ per the usual forrest processing, see input.xmap for more details.
+ </p>
</description>
</implementation>
</step>
</steps>
</useCase>
-
<useCase status="In Progress">
<title>Generate a Functionality Matrix</title>
<description>
- <p>If a use case document is correcly marked up with <code>fixme</code> elements it is possible
- to create a functionality matrix for each use case. This will show how complete the implementation
- of a use case is.</p>
-
- <p>A table can be created which shows each of the steps in a use case, each step can be given a
- count for the bumber of fixme items outstanding on each of the steps. Furthermore, since each
- <code>fixme</code> is given a priority we can clearly indicate which use cases are operational an
- hich are not.</p>
+ <p>
+ If a use case document is correcly marked up with <code>fixme</code>
+ elements it is possible to create a functionality matrix for each use
+ case. This will show how complete the implementation of a use case is.
+ </p>
+
+ <p>
+ A table can be created which shows each of the steps in a use case, each
+ step can be given a count for the bumber of fixme items outstanding on
+ each of the steps. Furthermore, since each <code>fixme</code> is given a
+ priority we can clearly indicate which use cases are operational an hich
+ are not.
+ </p>
</description>
-
<steps>
<step>
<title>Make HTTP request</title>
@@ -341,30 +387,42 @@
</description>
<result>
<p>
- An XDoc is created that lists the steps in each use case and identifies the status
- of each use case.
+ An XDoc is created that lists the steps in each use case and
+ identifies the status of each use case.
</p>
</result>
-
- <fixme priority="Blocker">Not Implemented Yet - although the user and dev use case documents
- do show the status of each step in the details table and implementation notes.</fixme>
-
+ <fixme priority="Blocker">
+ Not Implemented Yet - although the user and dev use case documents do
+ show the status of each step in the details table and implementation
+ notes.
+ </fixme>
<alternatives>
- <p>Depending on what plugins are available within your running instance of Forrest you will
- be able to request different output formats as per the usual Forrest usage. For example requesting
- a http://localhost:8888/docs/developer/featureMatrix/useCases.html will generate the HTML document, whilst
- http://localhost:8888/docs/developer/featureMatrix/useCases.pdf will generate the PDF document (as long
- as you have the relevant plugins installed).</p>
+ <p>
+ Depending on what plugins are available within your running instance
+ of Forrest you will be able to request different output formats as
+ per the usual Forrest usage. For example requesting a
+ http://localhost:8888/docs/developer/featureMatrix/useCases.html
+ will generate the HTML document, whilst
+ http://localhost:8888/docs/developer/featureMatrix/useCases.pdf will
+ generate the PDF document (as long as you have the relevant plugins
+ installed).
+ </p>
</alternatives>
-
<implementation>
<description>
- <p>The source document for use cases is, by default, called <code>useCases.xml</code> and is
- located in the root of the projects xdocs directory.</p>
-
- <p>The URL space <code>docs/**/useCases.xml</code> is reserved for the projectInfo plugin. A request to
- /docs/developer/featureMatrix/useCases.xml results in the useCases.xml file being translated into an XDoc as per
- the usual forrest processing. See the input.xmap file fo this plugin,</p>
+ <p>
+ The source document for use cases is, by default, called
+ <code>useCases.xml</code> and is located in the root of the
+ projects xdocs directory.
+ </p>
+
+ <p>
+ The URL space <code>docs/**/useCases.xml</code> is reserved for
+ the projectInfo plugin. A request to
+ /docs/developer/featureMatrix/useCases.xml results in the
+ useCases.xml file being translated into an XDoc as per the usual
+ forrest processing. See the input.xmap file fo this plugin,
+ </p>
</description>
</implementation>
</step>
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/images/project.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/images/project.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/index.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/index.html?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/index.html Tue Apr 10 19:03:32 2007
@@ -77,7 +77,7 @@
|breadtrail
+-->
<div class="breadtrail">
-
+
</div>
<!--+
@@ -196,92 +196,117 @@
</ul>
</li>
</ul>
-</div>
+</div>
<a name="N1000D"></a><a name="Apache+Forrest+-+org.apache.forrest.plugin.input.projectInfo+Plugin"></a>
<h2 class="underlined_10">Apache Forrest - org.apache.forrest.plugin.input.projectInfo Plugin</h2>
<div class="section">
-<p>This plugin generates project info from various configuration files.</p>
+<p>
+ This plugin generates project info from various configuration files.
+ </p>
</div>
-
<a name="N10017"></a><a name="Changes"></a>
<h2 class="underlined_10">Changes</h2>
<div class="section">
-<p>By maintaining a file called <span class="codefrag">status.xml</span> you can manage a list
- changes to your code base. This list can then be generated as a changes
- page and/or an RSS feed of those changes. For example, here are the
- <a href="changes.html">changes</a> for this plugin, here is the same
- list of changes as an <a href="changes.rss">RSS feed</a>.</p>
-<p>It's possible to limit the displayed changes to a particular version
- number as well. For example, here are the changes for
- <a href="changes_0.1.html">version 0.1</a> of this plugin (and
- as an <a href="changes_0.1.rss">RSS feed</a>).</p>
-<p>If you want to only retrieve the changes for the most recent version
- of the project then you can do that too. Here are the changes in the
- <a href="changes_current.html">current development version</a> of this
- plugin (and once more as an <a href="changes_current.rss">RSS feed</a>).</p>
+<p>
+ By maintaining a file called <span class="codefrag">status.xml</span> you can manage a
+ list changes to your code base. This list can then be generated as a
+ changes page and/or an RSS feed of those changes. For example, here are
+ the <a href="changes.html">changes</a> for this plugin, here is the same
+ list of changes as an <a href="changes.rss">RSS feed</a>.
+ </p>
+<p>
+ It's possible to limit the displayed changes to a particular version
+ number as well. For example, here are the changes for
+ <a href="changes_0.1.html">version 0.1</a> of this plugin (and as an
+ <a href="changes_0.1.rss">RSS feed</a>).
+ </p>
+<p>
+ If you want to only retrieve the changes for the most recent version of
+ the project then you can do that too. Here are the changes in the
+ <a href="changes_current.html">current development version</a> of this
+ plugin (and once more as an <a href="changes_current.rss">RSS feed</a>).
+ </p>
</div>
-
<a name="N10042"></a><a name="SVN+Changes"></a>
<h2 class="underlined_10">SVN Changes</h2>
<div class="section">
-<p>You can generate as well the changes with svn. For this you need to
- point forrest to the directory where the svn logs are. The defaut is
- set to <span class="codefrag">{properties:content}svn-log/</span> and you can change it by
- setting <span class="codefrag">projectInfo.svn.log.dir</span> in your project
- locationmap.</p>
-<p>We created a log file for demonstration with the following command:</p>
+<p>
+ You can generate as well the changes with svn. For this you need to
+ point forrest to the directory where the svn logs are. The defaut is set
+ to <span class="codefrag">{properties:content}svn-log/</span> and you can change it by
+ setting <span class="codefrag">projectInfo.svn.log.dir</span> in your project
+ locationmap.
+ </p>
+<p>
+ We created a log file for demonstration with the following command:
+ </p>
<pre class="code">
cd forrest/trunk/plugins/org.apache.forrest.plugin.input.projectInfo
svn log --xml -v . > src/documentation/content/svn-log/log.svn.xml</pre>
-<p>This file reflect all changes that have been done to this plugin. You
- can see the result <a href="log.svn.html">log.svn.html</a>.</p>
-<p>You see the only context we have definied is "code". This is
- controlled by a mapper file. The defaut is set to
- <span class="codefrag">{properties:content}path-to-context.xml</span> and you can change it
- by setting <span class="codefrag">projectInfo.svn.mapper</span> in your project
- locationmap.</p>
-<pre class="code"><paths>
+<p>
+ This file reflect all changes that have been done to this plugin. You
+ can see the result <a href="log.svn.html">log.svn.html</a>.
+ </p>
+<p>
+ You see the only context we have definied is "code". This is controlled
+ by a mapper file. The defaut is set to
+ <span class="codefrag">{properties:content}path-to-context.xml</span> and you can change
+ it by setting <span class="codefrag">projectInfo.svn.mapper</span> in your project
+ locationmap.
+ </p>
+<pre class="code">
+<paths>
<path context="Code">/forrest</path>
-</paths></pre>
-<p>If the log file is growing, one is looking into splitting the file.
- You can find out the revision number of the first and last commit of a
- month within the log by requesting <a href="log.svn-revision.xml">log.svn-revision.xml</a>.</p>
-<p>We implemented as well a small svn cli output to generate log files
- per month <a href="log.svn-sh.xml">log.svn-sh.xml</a>. The defaut url is set to
- <span class="codefrag">http://svn.myHost.org/repos</span> and you can change it
- by setting <span class="codefrag">project.svn.url</span> in your project
- locationmap.</p>
+</paths>
+ </pre>
+<p>
+ If the log file is growing, one is looking into splitting the file. You
+ can find out the revision number of the first and last commit of a month
+ within the log by requesting
+ <a href="log.svn-revision.xml">log.svn-revision.xml</a>.
+ </p>
+<p>
+ We implemented as well a small svn cli output to generate log files per
+ month <a href="log.svn-sh.xml">log.svn-sh.xml</a>. The defaut url is set
+ to <span class="codefrag">http://svn.myHost.org/repos</span> and you can change it by
+ setting <span class="codefrag">project.svn.url</span> in your project locationmap.
+ </p>
</div>
-
<a name="N10081"></a><a name="To+Do+List"></a>
<h2 class="underlined_10">To Do List</h2>
<div class="section">
-<p>The status.xml file can also be used to manage a list of todo items for
- the community. For example, here is a
- <a href="todo.html">psuedo todo list</a> for this plugin (our real todo list
- is managed in an Issue Tracker, one day we hope to add support for that
- here too).</p>
+<p>
+ The status.xml file can also be used to manage a list of todo items for
+ the community. For example, here is a <a href="todo.html">psuedo todo
+ list</a> for this plugin (our real todo list is managed in an Issue
+ Tracker, one day we hope to add support for that here too).
+ </p>
</div>
-
<a name="N1008F"></a><a name="Release+Notes"></a>
<h2 class="underlined_10">Release Notes</h2>
<div class="section">
-<p>To produce release notes you must maintain a <span class="codefrag">status.xml</span> file
- for your project and request a page with an URL such as
- <span class="codefrag">http://domain.com/releaseNotes_0.7-dev.html</span>, this will be produce
- the release notes for 0.7-dev.</p>
-<p>If the version number ends with <span class="codefrag">-dev</span> a warning will be included
- in the generated page, informing the reader that it is a development version and
- therefore the list of changes is incomplete.</p>
-<p>For a <span class="codefrag">status.xml</span> <span class="codefrag">action</span> toi be included in the
- release notes it must have an attribute <span class="codefrag">importance="high"</span>. When
- writing actions in <span class="codefrag">status.xml</span> you should write them with the
- following two questions in mind:</p>
+<p>
+ To produce release notes you must maintain a <span class="codefrag">status.xml</span>
+ file for your project and request a page with an URL such as
+ <span class="codefrag">http://domain.com/releaseNotes_0.7-dev.html</span>, this will be
+ produce the release notes for 0.7-dev.
+ </p>
+<p>
+ If the version number ends with <span class="codefrag">-dev</span> a warning will be
+ included in the generated page, informing the reader that it is a
+ development version and therefore the list of changes is incomplete.
+ </p>
+<p>
+ For a <span class="codefrag">status.xml</span> <span class="codefrag">action</span> toi be included in the
+ release notes it must have an attribute <span class="codefrag">importance="high"</span>.
+ When writing actions in <span class="codefrag">status.xml</span> you should write them
+ with the following two questions in mind:
+ </p>
<ul>
<li>should it be importance="high"?</li>
@@ -289,44 +314,58 @@
<li>will the action read correctly in the release notes?</li>
</ul>
-<p>The introductory text in the release notes comes from the (optional)
- element <span class="codefrag">notes</span> (a child of the <span class="codefrag">release</span> element).</p>
+<p>
+ The introductory text in the release notes comes from the (optional)
+ element <span class="codefrag">notes</span> (a child of the <span class="codefrag">release</span>
+ element).
+ </p>
<div class="note">
<div class="label">Note</div>
-<div class="content">The same options with respect to retrieveing specific versions of the
- release notes are available as with the changes feature (discuseed above).</div>
+<div class="content">
+ The same options with respect to retrieveing specific versions of the
+ release notes are available as with the changes feature (discuseed
+ above).
+ </div>
</div>
</div>
-
<a name="N100C9"></a><a name="Developers+List"></a>
<h2 class="underlined_10">Developers List</h2>
<div class="section">
-<p>The status.xml file can also contain a list of committers and
- contributors which can, optionally, be displayed as part of the changes file.</p>
-<p>At the time of writing this functionality is quite minimal, being just
- a list of authors at the end of the changes document. However, in future
- releases it is intended that a more configurable output will be
- available.</p>
+<p>
+ The status.xml file can also contain a list of committers and
+ contributors which can, optionally, be displayed as part of the changes
+ file.
+ </p>
+<p>
+ At the time of writing this functionality is quite minimal, being just a
+ list of authors at the end of the changes document. However, in future
+ releases it is intended that a more configurable output will be
+ available.
+ </p>
<a name="N100D5"></a><a name="Contributor+List"></a>
<h3 class="underlined_5">Contributor List</h3>
-<p>It may be that some items have been contributed by authors other
- than those listed in the developer list. These are accredited in a
- <span class="codefrag">due-to</span> attribute of the <span class="codefrag">action</span> element in
- status.xml. A list of this contributors is made available at the
- end of the release notes for each version.</p>
+<p>
+ It may be that some items have been contributed by authors other than
+ those listed in the developer list. These are accredited in a
+ <span class="codefrag">due-to</span> attribute of the <span class="codefrag">action</span> element in
+ status.xml. A list of this contributors is made available at the end
+ of the release notes for each version.
+ </p>
</div>
-
-
<a name="N100E6"></a><a name="Use+Cases"></a>
<h2 class="underlined_10">Use Cases</h2>
<div class="section">
-<p>Projects can manage a document describing various use cases for the
- application. These use cases can then be used to generate useful developer
- and user documentation, as well as helping to track the implementation
- status of features.</p>
-<p>Some of the uses of this feature are:</p>
+<p>
+ Projects can manage a document describing various use cases for the
+ application. These use cases can then be used to generate useful
+ developer and user documentation, as well as helping to track the
+ implementation status of features.
+ </p>
+<p>
+ Some of the uses of this feature are:
+ </p>
<ul>
<li>during design - what needs to be done</li>
@@ -338,7 +377,9 @@
<li>during maintenance - how something was implemented</li>
</ul>
-<p>To see some examples take a look at:</p>
+<p>
+ To see some examples take a look at:
+ </p>
<ul>
<li>
@@ -350,24 +391,29 @@
</ul>
</div>
-
<a name="N10114"></a><a name="Experimental+Features"></a>
<h2 class="underlined_10">Experimental Features</h2>
<div class="section">
-<p>These features are operational, however, they are not fully developed and
- may change considerably before they become part of the official feature set.
- You can use them, but be prepared for changes, possibly without warning. If you
- do use these features we recomend that you join the developers mailing list.</p>
+<p>
+ These features are operational, however, they are not fully developed
+ and may change considerably before they become part of the official
+ feature set. You can use them, but be prepared for changes, possibly
+ without warning. If you do use these features we recomend that you join
+ the developers mailing list.
+ </p>
<a name="N1011D"></a><a name="Configuration"></a>
<h3 class="underlined_5">Configuration</h3>
-<p>This plugin uses an experimental properties system that allows plugins
- to expose configuration information to the project. It is likely that at
- least some of these configuration options will eventually move into Dispatcher
- based contracts. In the meantime, you can use this config system to control
- some aspects of the display information. See the
- <span class="codefrag">forrest.properties.xml</span> file for a description of the config
- options available. To alter the configuration simply override these
- properties in your projects <span class="codefrag">forrest.properties.xml</span> file.</p>
+<p>
+ This plugin uses an experimental properties system that allows plugins
+ to expose configuration information to the project. It is likely that
+ at least some of these configuration options will eventually move into
+ Dispatcher based contracts. In the meantime, you can use this config
+ system to control some aspects of the display information. See the
+ <span class="codefrag">forrest.properties.xml</span> file for a description of the
+ config options available. To alter the configuration simply override
+ these properties in your projects <span class="codefrag">forrest.properties.xml</span>
+ file.
+ </p>
</div>
</div>
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/linkmap.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/linkmap.html?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/linkmap.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/linkmap.html Tue Apr 10 19:03:32 2007
@@ -77,7 +77,7 @@
|breadtrail
+-->
<div class="breadtrail">
-
+
</div>
<!--+
@@ -159,13 +159,14 @@
<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
</div>
<h1>Site Linkmap Table of Contents</h1>
-<p>This is a map of the complete site and its structure.</p>
+<p>
+ This is a map of the complete site and its structure.
+ </p>
<ul>
<li>
<a>org.apache.forrest.plugin.input.projectInfo</a> ___________________ <em>site</em>
</li>
<ul>
-
<ul>
<li>
@@ -208,7 +209,6 @@
<li>
<a href="todo.html">Todo</a> ___________________ <em>todo</em> : Todo List</li>
</ul>
-
<ul>
<li>
@@ -218,7 +218,6 @@
</ul>
</ul>
-
<ul>
<li>
<a href="docs/">Documentation</a> ___________________ <em>docs</em>
@@ -275,18 +274,15 @@
<a href="docs/developer/useCases/all.html">All Cases</a> ___________________ <em>all</em>
</li>
</ul>
-
+
</ul>
</ul>
</ul>
</ul>
-
-
-
</ul>
</ul>
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/locationmap.xml
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/locationmap.xml?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/locationmap.xml (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/locationmap.xml Tue Apr 10 19:03:32 2007
@@ -15,11 +15,8 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
<!-- Default Forrest locationmap -->
-
<locationmap xmlns="http://apache.org/forrest/locationmap/1.0">
-
<components>
<matchers default="lm">
<matcher
@@ -27,11 +24,10 @@
src="org.apache.forrest.locationmap.WildcardLocationMapHintMatcher"/>
</matchers>
<selectors default="exists">
- <selector name="exists" logger="sitemap.selector.exists"
+ <selector name="exists" logger="sitemap.selector.exists"
src="org.apache.forrest.sourceexists.SourceExistsSelector" />
</selectors>
</components>
-
<locator>
<match pattern="project.svn.url">
<location src="http://svn.apache.org/repos/asf/forrest/trunk/plugins/org.apache.forrest.plugin.input.projectInfo" />
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/log.svn.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/log.svn.html?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/log.svn.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/log.svn.html Tue Apr 10 19:03:32 2007
@@ -77,7 +77,7 @@
|breadtrail
+-->
<div class="breadtrail">
-
+
</div>
<!--+
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.1.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.1.html?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.1.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.1.html Tue Apr 10 19:03:32 2007
@@ -77,7 +77,7 @@
|breadtrail
+-->
<div class="breadtrail">
-
+
</div>
<!--+
@@ -182,12 +182,17 @@
<a name="N10009"></a><a name="PluginInfo+0.1"></a>
<h2 class="underlined_10">PluginInfo 0.1</h2>
<div class="section">
-<p>This plugin encapsulates and extends functionality that was originally in
- Forrest Core. With the advent of plugins in Forrest 0.7 we extracted the
- functionality for generating changes.xml and todo.xml from the status.xml file. It is
- intended that this functionality be extended further within this plugin.</p>
-<p>In fact, we have already extended the functionality in a couple of important
- ways. See the changelog for more details.</p>
+<p>
+ This plugin encapsulates and extends functionality that was
+ originally in Forrest Core. With the advent of plugins in Forrest
+ 0.7 we extracted the functionality for generating changes.xml and
+ todo.xml from the status.xml file. It is intended that this
+ functionality be extended further within this plugin.
+ </p>
+<p>
+ In fact, we have already extended the functionality in a couple of
+ important ways. See the changelog for more details.
+ </p>
</div>
</notes>
@@ -197,7 +202,8 @@
<div class="note">
<div class="label">Note</div>
<div class="content">This is not a complete list of changes, just some of the more important ones.
- A full list of changes in this release <a href="changes_0.1.html">is available</a>.</div>
+ A full list of changes in this release <a href="changes_0.1.html">is available</a>.
+ </div>
</div>
<a name="N10020"></a><a name="Changes+to+the+Code+Base"></a>
<h3 class="underlined_5">Changes to the Code Base</h3>
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.2-dev.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.2-dev.html?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.2-dev.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/releaseNotes_0.2-dev.html Tue Apr 10 19:03:32 2007
@@ -77,7 +77,7 @@
|breadtrail
+-->
<div class="breadtrail">
-
+
</div>
<!--+
@@ -182,8 +182,10 @@
<a name="N1000B"></a><a name="pluginInfo+0.2"></a>
<h2 class="underlined_10">pluginInfo 0.2</h2>
<div class="section">
-<p>This plugin provides various mechanisms for extracting and
- displaying information about one or more projects.</p>
+<p>
+ This plugin provides various mechanisms for extracting and
+ displaying information about one or more projects.
+ </p>
</div>
</notes>
@@ -193,7 +195,8 @@
<div class="note">
<div class="label">Note</div>
<div class="content">This is not a complete list of changes, just some of the more important ones.
- A full list of changes in this release <a href="changes_0.2-dev.html">is available</a>.</div>
+ A full list of changes in this release <a href="changes_0.2-dev.html">is available</a>.
+ </div>
</div>
<a name="N1001F"></a><a name="Changes+to+the+Code+Base"></a>
<h3 class="underlined_5">Changes to the Code Base</h3>
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/CommonMessages_es.xml
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/CommonMessages_es.xml?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/CommonMessages_es.xml (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/CommonMessages_es.xml Tue Apr 10 19:03:32 2007
@@ -21,4 +21,3 @@
<message key="Search">Buscar</message>
<message key="Search the site with">Buscar en</message>
</catalogue>
-
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-b-l-15-1body-2menu-3menu.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-b-l-15-1body-2menu-3menu.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-b-r-15-1body-2menu-3menu.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-b-r-15-1body-2menu-3menu.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-b-r-5-1header-2tab-selected-3tab-selected.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-b-r-5-1header-2tab-selected-3tab-selected.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-l-5-1header-2searchbox-3searchbox.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-l-5-1header-2searchbox-3searchbox.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-l-5-1header-2tab-selected-3tab-selected.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-l-5-1header-2tab-selected-3tab-selected.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-l-5-1header-2tab-unselected-3tab-unselected.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-l-5-1header-2tab-unselected-3tab-unselected.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-15-1body-2menu-3menu.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-15-1body-2menu-3menu.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-5-1header-2searchbox-3searchbox.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-5-1header-2searchbox-3searchbox.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-5-1header-2tab-selected-3tab-selected.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-5-1header-2tab-selected-3tab-selected.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-5-1header-2tab-unselected-3tab-unselected.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.projectInfo/skin/images/rc-t-r-5-1header-2tab-unselected-3tab-unselected.png?view=diff&rev=527368&r1=527367&r2=527368
==============================================================================
Binary files - no diff available.