DPML Notify

[mcconnell at BerliOS <mcconnell AT mail.berlios.de>]

Author: mcconnell
Date: 2006-08-09 19:04:42 +0200 (Wed, 09 Aug 2006)
New Revision: 1726

Modified:
   trunk/central/site/etc/docs/.htaccess
   trunk/central/site/src/docs/station/concepts/index.xml
   trunk/central/site/src/docs/transit/tutorials/navigation.xml
   trunk/central/site/src/docs/transit/tutorials/plugins.xml
   trunk/central/site/src/docs/util/cli/overview.xml
Log:
correcting links in docs

Modified: trunk/central/site/etc/docs/.htaccess
===================================================================
--- trunk/central/site/etc/docs/.htaccess       2006-08-09 05:55:36 UTC (rev 
1725)
+++ trunk/central/site/etc/docs/.htaccess       2006-08-09 17:04:42 UTC (rev 
1726)
@@ -16,6 +16,10 @@
 RedirectMatch ^/milestones/* http://download.dpml.net/milestones/index.html
 RedirectMatch ^/dpml/1.0.0-1692/* http://api.dpml.net/dpml/1.0.0/index.html
 RedirectMatch ^/dpml/1.0.0-RC* http://api.dpml.net/dpml/1.0.0/index.html
-RedirectMatch ^/reports/1.0.0-RC* 
http://api.dpml.net/reports/1.0.0/index.html
-RedirectMatch ^/reports/2005* http://api.dpml.net/reports/1.0.0/index.html
-RedirectMatch ^/reports/2006* http://api.dpml.net/reports/1.0.0/index.html
+RedirectMatch ^/reports/1.0.0-RC* 
http://www.dpml.net/about/reports/index.html
+RedirectMatch ^/reports/2005* http://www.dpml.net/about/reports/index.html
+RedirectMatch ^/reports/2006* http://www.dpml.net/about/reports/index.html
+RedirectMatch ^/api/dpml/metro/* http://api.dpml.net/dpml/1.0.0/index.html
+RedirectMatch ^/api/dpml/2006* http://api.dpml.net/dpml/1.0.0/index.html
+RedirectMatch ^/api/dpml/2005* http://api.dpml.net/dpml/1.0.0/index.html
+

Modified: trunk/central/site/src/docs/station/concepts/index.xml
===================================================================
--- trunk/central/site/src/docs/station/concepts/index.xml      2006-08-09 
05:55:36 UTC (rev 1725)
+++ trunk/central/site/src/docs/station/concepts/index.xml      2006-08-09 
17:04:42 UTC (rev 1726)
@@ -14,10 +14,10 @@
       <p>
       The DPML Station is system supporting the maintenance of multiple
       applications. It is composed of an remotely accessible registry
-      of <a href="applications/index.html">applications</a> and a 
-      supporting <a href="cli/index.html">commandline tool</a>.
+      of <a href="../applications/index.html">applications</a> and a 
+      supporting <a href="../cli/index.html">commandline tool</a>.
       Applications are defined using network resolvable 
-      <a href="profiles/index.html">profiles</a> that contain information 
about
+      <a href="../profiles/index.html">profiles</a> that contain information 
about
       the application environment, JVM settings, and application codebase.
       </p>
 

Modified: trunk/central/site/src/docs/transit/tutorials/navigation.xml
===================================================================
--- trunk/central/site/src/docs/transit/tutorials/navigation.xml        
2006-08-09 05:55:36 UTC (rev 1725)
+++ trunk/central/site/src/docs/transit/tutorials/navigation.xml        
2006-08-09 17:04:42 UTC (rev 1726)
@@ -29,7 +29,7 @@
       <item name="Resource Management" href="overview.html"/>
       <item name="Artifact Protocol" href="artifacts.html"/>
       <item name="Local Protocol" href="local.html"/>
-      <!--<item name="Working with Plugins" href="plugins.html"/>-->
+      <item name="Plugin Services" href="plugins.html"/>
       <item name="Repositories" href="repositories.html"/>
     </menu>
 

Modified: trunk/central/site/src/docs/transit/tutorials/plugins.xml
===================================================================
--- trunk/central/site/src/docs/transit/tutorials/plugins.xml   2006-08-09 
05:55:36 UTC (rev 1725)
+++ trunk/central/site/src/docs/transit/tutorials/plugins.xml   2006-08-09 
17:04:42 UTC (rev 1726)
@@ -44,65 +44,11 @@
         to provide a framework for plugable sub-systems deployment.
         </p>
 
-      </subsection>
-
-      <subsection name="Part Creation">
-
         <p>
-        In practice the creation and maintenance of plugin information is 
highly 
-        error prone due to overall complexity of dependency management. This 
was one
-        of the driving factors in the development of the Depot build system. 
 Depot 
-        was developed from the ground up to provided full transitive 
-        dependency management across build, runtime and test scopes. Using 
the 
-        Depot project model the job of creating a plugin definition is 
reduced down 
-        to type production declaration within a Depot project definition.
+        The following part description is an example that has been 
automaticaly generated 
+        by the Depot build system.
         </p>
         
-        <p><i>An example Depot project defintion ...</i></p>
-
-<pre>
-&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
-&lt;index xmlns="link:xsd:dpml/lang/dpml-module#1.0"&gt;
-
-  ...
-  
-  &lt;project name="dpml-metro-runtime" basedir="runtime"&gt;
-    &lt;info title="Metro Runtime"&gt;
-      &lt;description&gt;
-      DPML Component management platform runtime container.
-      &lt;/description&gt;
-    &lt;/info&gt;
-    &lt;types&gt;
-      &lt;type id="jar"/&gt;
-      <font color="darkred">&lt;part:plugin alias="true" 
class="net.dpml.metro.runtime.CompositionController"/&gt;</font>
-    &lt;/types&gt;
-    &lt;dependencies&gt;
-      &lt;include ref="dpml/util/dpml-logging-api" tag="public"/&gt;
-      &lt;include key="dpml-metro-component" tag="protected"/&gt;
-      &lt;include key="dpml-metro-model" tag="protected"/&gt;
-    &lt;/dependencies&gt;
-    &lt;dependencies scope="test"&gt;
-      &lt;include ref="ant/ant-junit"/&gt;
-    &lt;/dependencies&gt;
-  &lt;/project&gt;
-   
-  ...
-  
-&lt;/index&gt;
-</pre>
-
-        <p>
-        The following part description is generated automatically by the 
Depot build system
-        based on the above project definition based on the following rules:
-        </p>
-        
-        <ul>
-          <li>The <tt>info</tt> element is mapped directory to a part info 
declaration.</li>
-          <li>The <tt>part:plugin</tt> element is mapped to a part 
deployment <tt>strategy</tt> 
-              definition.</li>
-          <li>All runtime dependencies are fully expanded.</li>
-        </ul>
-        
         <source><![CDATA[<?xml version="1.0"?>
 
 <part xmlns="link:xsd:dpml/lang/dpml-part#1.0"
@@ -183,10 +129,9 @@
       <subsection name="Summary">
       
         <p>
-        In the examples presented above we have demonstrated the usage of 
Depot's project 
-        definition as the source of information about project runtime 
dependencies and 
-        deployment information from which a part definition is created and 
used at runtime
-        within an application.  The next tutorial focussed on the <a 
href="repositories.html">
+        In the examples presented above we have demonstrated the usage of an 
XML definition of 
+        a part including a classloader defintion and object deployment 
strategy.  The next 
+        tutorial focussed on the <a href="repositories.html">
         underlying resource repositories</a> from which artifact uris are 
resolved in terms of 
         physical resources.
         </p>

Modified: trunk/central/site/src/docs/util/cli/overview.xml
===================================================================
--- trunk/central/site/src/docs/util/cli/overview.xml   2006-08-09 05:55:36 
UTC (rev 1725)
+++ trunk/central/site/src/docs/util/cli/overview.xml   2006-08-09 17:04:42 
UTC (rev 1726)
@@ -96,8 +96,7 @@
         .create();
                 </source>
                 <p>
-                    The <a href="options.html">Options</a> and 
-                    <a href="builders.html">Builders</a> sections of the 
manual discuss these 
+                    The <a href="options.html">Options</a> section of the 
manual discuss these 
                     features in greater detail.
                 </p>
                 <p>
@@ -120,8 +119,7 @@
                     to the user in a manner typical of command line 
applications.  The 
                     HelpFormatter is designed with flexibility in mind so it 
should be possible to 
                     control exactly which structures are described to the 
user and what level of 
-                    detail to use.  The HelpFormatter is discussed in detail 
in the 
-                    <a href="utilities.html#HelpFormatter">Utilities</a> 
section of the manual.
+                    detail to use.
                 </p>
                 <p>
                     Any errors that occur while parsing result in an 
OptionException being thrown 
@@ -189,9 +187,7 @@
                     provided that can wrap a Properties or Preferences 
instance as a CommandLine.
                     These can then be combined with the 
DefaultingCommandLine and the parsed 
                     CommandLine to provide a variety of different defaulting 
and overriding 
-                    scenarios.  The CommandLine interface and 
implementations are discussed 
-                    further in the <a 
href="commandlines.html">CommandLines</a> section of the 
-                    manual.
+                    scenarios.
                 </p>
             </subsection>
         </section>