Author: buildbot
Date: Wed May 29 07:43:14 2013
New Revision: 863590
Log:
Staging update by buildbot for ace
Modified:
websites/staging/ace/trunk/content/ (props changed)
websites/staging/ace/trunk/content/user-doc/introduction.html
Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 29 07:43:14 2013
@@ -1 +1 @@
-1471160
+1487374
Modified: websites/staging/ace/trunk/content/user-doc/introduction.html
==============================================================================
--- websites/staging/ace/trunk/content/user-doc/introduction.html (original)
+++ websites/staging/ace/trunk/content/user-doc/introduction.html Wed May 29
07:43:14 2013
@@ -178,7 +178,7 @@
<p>Keeping track of what is installed where becomes quite a challenge if the
number of components and targets grows, and this is where Apache ACE comes
in.</p>
<p>Apache ACE is a software distribution framework. It is written as a set of
OSGi components and consists of three major subsystems:</p>
<ol>
-<li>dependency management, which handles the complexity of managing the
dependencies between component, aggregating them into groups and licenses and
associating those to targets</li>
+<li>dependency management, which handles the complexity of managing the
dependencies between component, aggregating them into features and
distributions and associating those to targets</li>
<li>deployment management, which ensures that the right components get
installed onto the right targets in a robust and scalable way</li>
<li>feedback management, which collects life cycle feedback on the target and
aggregates that on a central server</li>
</ol>
