svn commit: r1525435 - /felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-background.mdtext

[pd...@apache.org]

Author: pderop
Date: Sun Sep 22 20:23:36 2013
New Revision: 1525435

URL: http://svn.apache.org/r1525435
Log:
CMS migration ...

Modified:
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-background.mdtext

Modified: felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-background.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-background.mdtext?rev=1525435&r1=1525434&r2=1525435&view=diff
==============================================================================
--- felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-background.mdtext (original)
+++ felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-background.mdtext Sun Sep 22 20:23:36 2013
@@ -4,6 +4,7 @@ Title: Apache Felix Dependency Manager -
 ## Background
 
 In an OSGi framework, services are deployed using bundles and these bundles feature two types of dependencies: 
+
 1. Package dependencies. A bundle can export a package which others import. These dependencies, although dynamic, are relatively easy to handle and the whole resolution process is handled by the OSGi framework for you.
 1. Service dependencies. Services, implemented by components inside of bundles, can have their own life cycle within that of their containing bundle and therefore can be registered and unregistered at any time. Other components often depend on these services and need to deal with changes in their availability. 
 
@@ -17,9 +18,10 @@ In real implementations, you are probabl
 
 The Dependency Manager provides you with the right building blocks to declaratively specify dependencies using a straightforward Java API that is easy to maintain and refactor.
 
-### Design Goals
+## Design Goals
 
 The goals that drove the design of the dependency manager are:
+
 * Provide a clean separation between a component implementation and the "glue" that binds it to the OSGi framework. The component implementation should not have to contain any OSGi specific code. In other words, it should be a POJO (Plain Old Java Object).
 * Minimize the amount of code that needs to be written. The specification and management of dependencies should be automated as much as possible, whilst still providing enough flexibility to customize the system.
 * Be extensible. Even though the core bundle provides a lot of different dependencies already, you should be able to add your own types of dependencies easily.