Update docs

Author: slachiewicz

src/site/apt/index.apt

@@ -18,15 +18,13 @@ Overview
 
     * {{{./plexus-archiver/}plexus-archiver}}: components to manipulate archives,
 
-    * {{{./plexus-cli/}plexus-cli}}: components to easily create CLIs,
-
     * {{{./plexus-compiler/}plexus-compiler}}: components to manipulate compilers,
 
-    * {{{./plexus-digest/}plexus-digest}}: 
+    * {{{./plexus-digest/}plexus-digest}}:
 
-    * {{{./plexus-i18n/}plexus-i18n}}: 
+    * {{{./plexus-i18n/}plexus-i18n}}:
 
-    * {{{./plexus-interactivity/}plexus-interactivity}}: 
+    * {{{./plexus-interactivity/}plexus-interactivity}}:
 
     * {{{./plexus-interpolation/}plexus-interpolation}}: flexible interpolation framework,
 
@@ -36,19 +34,11 @@ Overview
 
     * {{{./plexus-resources/}plexus-resources}}: a component to transparently retrieve resources from the filesystem, classpath or internet,
 
-    * {{{./plexus-swizzle/}plexus-swizzle}}: a component adaptated from David Blevin's Swizzle project to generate reports from an issue tracking system (JIRA),
-
     * {{{./plexus-velocity/}plexus-velocity}}: component to render velocity templates.
 
     []
 
-  * Plexus Parent POMs:
-
-    * {{{./plexus-pom/}plexus}}
-
-    * {{{./plexus-components/}plexus-components}}
-
-    []
+  * Plexus Parent POM: {{{./plexus-pom/}plexus}}
 
   * {{{./plexus-utils/} Plexus Utils}},
 
@@ -69,48 +59,11 @@ Plexus History
 
 ============================
 
-  The Plexus project provides a full software stack for creating and executing software projects. Based on the
-  Plexus container, the applications can utilise component-oriented programming to build modular, reusable components
-  that can easily be assembled and reused.
-
-  While Plexus is similar to other <inversion-of-control> (IoC) or <dependency injection> frameworks such as the
-  Spring Framework, it is a full-fledged container that supports many more features such as:
-  
-    * Component lifecycles 
-
-    * Component instantiation strategies
-    
-    * Nested containers  
-    
-    * Component configuration
-    
-    * Auto-wiring
-    
-    * Component dependencies, and 
-
-    * Various dependency injection techniques including constructor injection, setter injection, and private field
-  injection. 
-  
-  
   See the {{{./ref/feature-comparison.html} Feature Comparison}} page for more information on
   the differences between Plexus and other products.
 
   The Plexus project provides a number of pre-built components for common tasks and toolkits
-  such as Jetty, Velocity, Hibernate, i18n, and {{{./ref/available-components.html} many more}}. However,
-  Plexus is also able to reuse your existing components written for other IoC frameworks such as
-  Spring, Avalon and Pico Container unmodified, as well as allowing you to reuse your existing code
-  inside the Plexus Container.
-
-  Plexus comes with an application server that can run your applications, making it trivial to
-  build a standalone executable distribution with common features such as service execution if needed.
-  However, Plexus applications can be run in any environment by embedding the container in an existing
-  application, including Java EE applications or web applications.
-
-  Components in Plexus need not be written in Java, with component factories existing for
-  Jython, JRuby, Beanshell, and Groovy.
-
-  The Plexus container is currently used in a number of applications and frameworks, most notably Maven 2.0 and
-  Webwork 2.2 (Struts Action Framework 2.0).
+  such as Velocity, i18n, and {{{./ref/available-components.html} many more}}.
 
   For answers to common questions about Plexus, see the {{{./faq.html} FAQ}}.