You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by bu...@apache.org on 2012/07/09 09:14:12 UTC

svn commit: r825100 - in /websites/staging/ace/trunk/content: ./ index.html

Author: buildbot
Date: Mon Jul  9 07:14:11 2012
New Revision: 825100

Log:
Staging update by buildbot for ace

Modified:
    websites/staging/ace/trunk/content/   (props changed)
    websites/staging/ace/trunk/content/index.html

Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul  9 07:14:11 2012
@@ -1 +1 @@
-1358936
+1358938

Modified: websites/staging/ace/trunk/content/index.html
==============================================================================
--- websites/staging/ace/trunk/content/index.html (original)
+++ websites/staging/ace/trunk/content/index.html Mon Jul  9 07:14:11 2012
@@ -156,6 +156,7 @@
       <h1>Apache ACE</h1>
       <div class="clear"></div>
       <div id="content"><p>Apache ACE is a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be.</p>
+<p>Apache ACE is an <a href="http://www.apache.org/">Apache</a> project, and as such is part of a larger community of users and developers.</p>
 <h1 id="background">Background</h1>
 <p>When assembling software out of reusable components, the task of deploying software onto an ever increasing number of targets is not trivial to solve. This becomes even harder when these targets require different components based on who's using them.</p>
 <p>Apache ACE allows you to group those components and assign them to a managed set of targets. This allows you to distribute updates and new components easily, while keeping a full history of what was installed where during what period. It also helps you setup an automated development, QA/testing, staging and production environment.</p>