You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@celix.apache.org by bu...@apache.org on 2015/07/08 14:47:34 UTC
svn commit: r957517 [1/2] - in /websites/staging/celix/trunk/content: ./
asf/ community/ community/boardreports/ community/contributing/
documentation/ examples/ subprojects/ support/
Author: buildbot
Date: Wed Jul 8 12:47:33 2015
New Revision: 957517
Log:
Staging update by buildbot for celix
Modified:
websites/staging/celix/trunk/content/ (props changed)
websites/staging/celix/trunk/content/asf/asf.html
websites/staging/celix/trunk/content/asf/links.html
websites/staging/celix/trunk/content/background-links.html
websites/staging/celix/trunk/content/background.html
websites/staging/celix/trunk/content/celix-links.html
websites/staging/celix/trunk/content/celix.html
websites/staging/celix/trunk/content/community/boardreports/boardreports.html
websites/staging/celix/trunk/content/community/boardreports/reports.html
websites/staging/celix/trunk/content/community/community.html
websites/staging/celix/trunk/content/community/contributing/contributing.html
websites/staging/celix/trunk/content/community/contributing/links.html
websites/staging/celix/trunk/content/community/links.html
websites/staging/celix/trunk/content/documentation.html
websites/staging/celix/trunk/content/documentation/buildingandrunning-links.html
websites/staging/celix/trunk/content/documentation/buildingandrunning.html
websites/staging/celix/trunk/content/documentation/design.html
websites/staging/celix/trunk/content/documentation/examples.html
websites/staging/celix/trunk/content/documentation/getting_started.html
websites/staging/celix/trunk/content/documentation/mapping.html
websites/staging/celix/trunk/content/documentation/memorypools.html
websites/staging/celix/trunk/content/documentation/releasing-links.html
websites/staging/celix/trunk/content/documentation/releasing.html
websites/staging/celix/trunk/content/download-links.html
websites/staging/celix/trunk/content/download.html
websites/staging/celix/trunk/content/examples/helloworld-links.html
websites/staging/celix/trunk/content/examples/helloworld.html
websites/staging/celix/trunk/content/index.html
websites/staging/celix/trunk/content/links.html
websites/staging/celix/trunk/content/subprojects.html
websites/staging/celix/trunk/content/subprojects/dependencymanager.html
websites/staging/celix/trunk/content/subprojects/deviceaccess.html
websites/staging/celix/trunk/content/subprojects/examples.html
websites/staging/celix/trunk/content/subprojects/framework.html
websites/staging/celix/trunk/content/subprojects/hessian.html
websites/staging/celix/trunk/content/subprojects/launcher.html
websites/staging/celix/trunk/content/subprojects/logservice.html
websites/staging/celix/trunk/content/subprojects/logwriter.html
websites/staging/celix/trunk/content/subprojects/remoteserviceadmin.html
websites/staging/celix/trunk/content/subprojects/shell.html
websites/staging/celix/trunk/content/subprojects/shelltui.html
websites/staging/celix/trunk/content/subprojects/utils.html
websites/staging/celix/trunk/content/support/issuetracking.html
websites/staging/celix/trunk/content/support/links.html
websites/staging/celix/trunk/content/support/mailinglist.html
websites/staging/celix/trunk/content/support/support.html
Propchange: websites/staging/celix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 8 12:47:33 2015
@@ -1 +1 @@
-1689848
+1689863
Modified: websites/staging/celix/trunk/content/asf/asf.html
==============================================================================
--- websites/staging/celix/trunk/content/asf/asf.html (original)
+++ websites/staging/celix/trunk/content/asf/asf.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Apache Software Foundation</h1>
- <p>Apache Celix is an effort undergoing incubation at The Apache Software Foundation (ASF), more information
+ <p class="title">Apache Software Foundation</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Apache Celix is an effort undergoing incubation at The Apache Software Foundation (ASF), more information
about ASF can be found at the following links:</p>
<ul>
<li><a href="http://www.apache.org/">ASF Home</a></li>
Modified: websites/staging/celix/trunk/content/asf/links.html
==============================================================================
--- websites/staging/celix/trunk/content/asf/links.html (original)
+++ websites/staging/celix/trunk/content/asf/links.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,7 +140,7 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
+ <p class="title"></p>
</div>
<div id="homeright">
Modified: websites/staging/celix/trunk/content/background-links.html
==============================================================================
--- websites/staging/celix/trunk/content/background-links.html (original)
+++ websites/staging/celix/trunk/content/background-links.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
- <h2 id="useful-links">Useful Links</h2>
+ <p class="title"></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://en.wikipedia.org/wiki/Dynamic_loading">Dynamic Loading</a><ul>
<li><a href="http://www.opengroup.org/onlinepubs/000095399/basedefs/dlfcn.h.html">Posix Dynamic Linking</a></li>
Modified: websites/staging/celix/trunk/content/background.html
==============================================================================
--- websites/staging/celix/trunk/content/background.html (original)
+++ websites/staging/celix/trunk/content/background.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Background</h1>
- <p>Celix started during the summer of 2010 as a simple project to see if it is possible to dynamically load libraries
+ <p class="title">Background</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Celix started during the summer of 2010 as a simple project to see if it is possible to dynamically load libraries
(at runtime) in C. After some initial testing and searching this is supported out of the box using Dynamic Loading.</p>
<p>Since Dynamic Loading only solves how libraries can be loaded and used, a framework has to be made to integrate it in.
For Java such frameworks exists, with OSGi being one of the leading specifications. OSGi provides guidelines for
@@ -176,7 +198,18 @@ awereness and implement Celix.</p>
<div id="download" class="rc">
- <h2 id="useful-links">Useful Links</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://en.wikipedia.org/wiki/Dynamic_loading">Dynamic Loading</a><ul>
<li><a href="http://www.opengroup.org/onlinepubs/000095399/basedefs/dlfcn.h.html">Posix Dynamic Linking</a></li>
Modified: websites/staging/celix/trunk/content/celix-links.html
==============================================================================
--- websites/staging/celix/trunk/content/celix-links.html (original)
+++ websites/staging/celix/trunk/content/celix-links.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
- <h2 id="useful-links">Useful Links</h2>
+ <p class="title"></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://www.osgi.org/Main/HomePage">OSGi</a><ul>
<li><a href="http://www.osgi.org/Specifications/HomePage">OSGi Specification</a></li>
Modified: websites/staging/celix/trunk/content/celix.html
==============================================================================
--- websites/staging/celix/trunk/content/celix.html (original)
+++ websites/staging/celix/trunk/content/celix.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">About Celix</h1>
- <p>Celix is an implementation of the OSGi specification adapted to C. It will follow the API as close as possible,
+ <p class="title">About Celix</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Celix is an implementation of the OSGi specification adapted to C. It will follow the API as close as possible,
but since the OSGi specification is written primarily for Java, there will be differences (Java is OO, C is procedural).
An important aspect of the implementation is interoperability between Java and C.
This interoperability is achieved by porting and implementing the Remote Services specification in Celix.</p>
@@ -141,7 +163,18 @@ This interoperability is achieved by por
<div id="download" class="rc">
- <h2 id="useful-links">Useful Links</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://www.osgi.org/Main/HomePage">OSGi</a><ul>
<li><a href="http://www.osgi.org/Specifications/HomePage">OSGi Specification</a></li>
Modified: websites/staging/celix/trunk/content/community/boardreports/boardreports.html
==============================================================================
--- websites/staging/celix/trunk/content/community/boardreports/boardreports.html (original)
+++ websites/staging/celix/trunk/content/community/boardreports/boardreports.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,11 +140,22 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Board Reports</h1>
- <p>To monitor incubator project, the Apache Software Foundation board holds monthly meetings.
+ <p class="title">Board Reports</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>To monitor incubator project, the Apache Software Foundation board holds monthly meetings.
For these meetings a board report must be delivered to the Incubator PMC.</p>
<p>On this page the reports for Celix are shown.</p>
-<h2 id="2013-10"><a href="http://wiki.apache.org/incubator/October2013">2013-10</a></h2>
+<h2 id="2013-10"><a href="http://wiki.apache.org/incubator/October2013">2013-10</a><a class="headerlink" href="#2013-10" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.</p>
<p>Celix has been incubating since 2010-11-02.</p>
@@ -161,7 +183,7 @@ Work for a new release is still ongoing,
<li>2013-01-07 Roman Shaposhnik joins as a mentor.</li>
<li>2012-03-20 Pepijn elected as committer.</li>
</ul>
-<h2 id="2013-07"><a href="http://wiki.apache.org/incubator/July2013">2013-07</a></h2>
+<h2 id="2013-07"><a href="http://wiki.apache.org/incubator/July2013">2013-07</a><a class="headerlink" href="#2013-07" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.</p>
<p>Celix has been incubating since 2010-11-02.</p>
@@ -190,7 +212,7 @@ Also work is underway to make a second r
16-12-2012</p>
<p>[ 1 ] https://www.osgi.org/bugzilla/show_bug.cgi?id=165</p>
<p>[ 2 ] http://incubator.markmail.org/thread/fza43iypjutcw2rm</p>
-<h2 id="2013-04"><a href="http://wiki.apache.org/incubator/April2013">2013-04</a></h2>
+<h2 id="2013-04"><a href="http://wiki.apache.org/incubator/April2013">2013-04</a><a class="headerlink" href="#2013-04" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.</p>
<p>Celix has been incubating since 2010-11-02.</p>
@@ -209,7 +231,7 @@ There is no active growth, but there is
<p>How has the project developed since the last report?
Technically progress has been slow the last months. There was a hackaton organized for remote services in Java [ 1 ], which although not directly related to Apache Celix, should eventually work together with the Apache Celix and as result the committers of Apache Celix where present. We also expect an increase in contributions the coming months because of the student intership / GSoC activities.</p>
<p>[ 1 ] http://lists.amdatu.org/pipermail/dev/2013-March/000020.html</p>
-<h2 id="2013-01"><a href="http://wiki.apache.org/incubator/January2013">2013-01</a></h2>
+<h2 id="2013-01"><a href="http://wiki.apache.org/incubator/January2013">2013-01</a><a class="headerlink" href="#2013-01" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an OSGi like implementation in C with a distinct focus on interoperability between Java and C.</p>
<p>Celix has been incubating since 2010-11-02.</p>
@@ -228,7 +250,7 @@ None.</p>
<p>How has the project developed since the last report?</p>
<p>A first release has been made. After struggling with several problems, consensus has been reached to solve these in a next release.
On a technical note, Celix now also compiles and runs on Win32 platforms.</p>
-<h2 id="2012-10"><a href="http://wiki.apache.org/incubator/October2012">2012-10</a></h2>
+<h2 id="2012-10"><a href="http://wiki.apache.org/incubator/October2012">2012-10</a><a class="headerlink" href="#2012-10" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C. </p>
<p>Celix entered incubation on November 2, 2010. </p>
@@ -258,7 +280,7 @@ based on the shepherd's view from last r
</li>
</ul>
<p>Signed off by mentor: marrs</p>
-<h2 id="2012-07"><a href="http://wiki.apache.org/incubator/July2012">2012-07</a></h2>
+<h2 id="2012-07"><a href="http://wiki.apache.org/incubator/July2012">2012-07</a><a class="headerlink" href="#2012-07" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -285,7 +307,7 @@ Details for Native-OSGi can be found at
Since the implementation is moving forward (al be it slowly), the community growth is the biggest concern for Celix.</p>
<p>Signed off by mentor:</p>
<p>Shepherd: Matt Franklin</p>
-<h2 id="2012-04"><a href="http://wiki.apache.org/incubator/April2012">2012-04</a></h2>
+<h2 id="2012-04"><a href="http://wiki.apache.org/incubator/April2012">2012-04</a><a class="headerlink" href="#2012-04" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -328,7 +350,7 @@ Over the next half year we will work out
<p>In <a href="http://markmail.org/thread/a3qltqhsocmrnerd">3</a> a list of similar projects is mentioned. Reaching out to these projects and trying to find a common ground on requirements/API etc could benefit Celix (and those projects as well).
To see if there is a common ground we need to contact those projects and plan a meeting.</p>
<p>Signed off by mentor:</p>
-<h2 id="2012-01"><a href="http://wiki.apache.org/incubator/January2012">2012-01</a></h2>
+<h2 id="2012-01"><a href="http://wiki.apache.org/incubator/January2012">2012-01</a><a class="headerlink" href="#2012-01" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -342,7 +364,7 @@ To see if there is a common ground we ne
<p>Signed off by mentor: marrs</p>
-<h2 id="2011-10"><a href="http://wiki.apache.org/incubator/October2011">2011-10</a></h2>
+<h2 id="2011-10"><a href="http://wiki.apache.org/incubator/October2011">2011-10</a><a class="headerlink" href="#2011-10" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -357,7 +379,7 @@ Also, in november a talk and demo will b
<p>Signed off by mentor:</p>
-<h2 id="2011-07"><a href="http://wiki.apache.org/incubator/July2011">2011-07</a></h2>
+<h2 id="2011-07"><a href="http://wiki.apache.org/incubator/July2011">2011-07</a><a class="headerlink" href="#2011-07" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -379,7 +401,7 @@ Also parts of Celix have been ported to
<p>Signed off by mentor:</p>
-<h2 id="2011-04"><a href="http://wiki.apache.org/incubator/April2011">2011-04</a></h2>
+<h2 id="2011-04"><a href="http://wiki.apache.org/incubator/April2011">2011-04</a><a class="headerlink" href="#2011-04" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -399,7 +421,7 @@ updating, possibly in combination with A
<p>Signed off by mentor:</p>
-<h2 id="2011-02"><a href="http://wiki.apache.org/incubator/February2011">2011-02</a></h2>
+<h2 id="2011-02"><a href="http://wiki.apache.org/incubator/February2011">2011-02</a><a class="headerlink" href="#2011-02" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -413,7 +435,7 @@ etc with APR functions.</p>
Move all "sub" project to the new structure.
Use APR for all file handling, threading etc.</p>
<p>Signed off by mentor:</p>
-<h2 id="2011-01"><a href="http://wiki.apache.org/incubator/January2011">2011-01</a></h2>
+<h2 id="2011-01"><a href="http://wiki.apache.org/incubator/January2011">2011-01</a><a class="headerlink" href="#2011-01" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -430,7 +452,7 @@ provides a great opportunity to increase
<p>Signed off by mentor: marrs </p>
-<h2 id="2010-12"><a href="http://wiki.apache.org/incubator/December2010">2010-12</a></h2>
+<h2 id="2010-12"><a href="http://wiki.apache.org/incubator/December2010">2010-12</a><a class="headerlink" href="#2010-12" title="Permanent link">¶</a></h2>
<p>= Celix =</p>
<p>Celix is an implementation of the OSGi Specification in C.</p>
<p>Celix entered incubation on November 2, 2010.</p>
@@ -449,7 +471,18 @@ SVN, and the project site is being creat
<div id="download" class="rc">
- <h2 id="links">Links</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="links">Links<a class="headerlink" href="#links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://wiki.apache.org/incubator/">Apache Incubator Wiki</a><ul>
<li><a href="http://wiki.apache.org/incubator/ReportingSchedule">Reporting Schedule</a></li>
Modified: websites/staging/celix/trunk/content/community/boardreports/reports.html
==============================================================================
--- websites/staging/celix/trunk/content/community/boardreports/reports.html (original)
+++ websites/staging/celix/trunk/content/community/boardreports/reports.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
- <h2 id="links">Links</h2>
+ <p class="title"></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="links">Links<a class="headerlink" href="#links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://wiki.apache.org/incubator/">Apache Incubator Wiki</a><ul>
<li><a href="http://wiki.apache.org/incubator/ReportingSchedule">Reporting Schedule</a></li>
Modified: websites/staging/celix/trunk/content/community/community.html
==============================================================================
--- websites/staging/celix/trunk/content/community/community.html (original)
+++ websites/staging/celix/trunk/content/community/community.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Celix Community</h1>
- <p>Celix is a community driven project, where everyone is free to download and use it. Besides using Celix we encourage
+ <p class="title">Celix Community</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Celix is a community driven project, where everyone is free to download and use it. Besides using Celix we encourage
everyone to participate in the development. This can be as simple as providing feedback and reporting bugs but could as
well mean bug fixes and code contributions.</p>
<ul>
Modified: websites/staging/celix/trunk/content/community/contributing/contributing.html
==============================================================================
--- websites/staging/celix/trunk/content/community/contributing/contributing.html (original)
+++ websites/staging/celix/trunk/content/community/contributing/contributing.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Contributing</h1>
- <p>The Celix community is open for everyone to participate in. Discussions are done over the
+ <p class="title">Contributing</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The Celix community is open for everyone to participate in. Discussions are done over the
<a href="/support/mailinglist.html">mailing lists</a>, and <a href="/support/issuetracking.html">issues</a> can be created and
seen by everyone.</p>
<p>If you would like to join the Celix community, a good start would be to follow the mailing list and participate in the
Modified: websites/staging/celix/trunk/content/community/contributing/links.html
==============================================================================
--- websites/staging/celix/trunk/content/community/contributing/links.html (original)
+++ websites/staging/celix/trunk/content/community/contributing/links.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,7 +140,7 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
+ <p class="title"></p>
</div>
<div id="homeright">
Modified: websites/staging/celix/trunk/content/community/links.html
==============================================================================
--- websites/staging/celix/trunk/content/community/links.html (original)
+++ websites/staging/celix/trunk/content/community/links.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,7 +140,7 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
+ <p class="title"></p>
</div>
<div id="homeright">
Modified: websites/staging/celix/trunk/content/documentation.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation.html (original)
+++ websites/staging/celix/trunk/content/documentation.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Documentation</h1>
- <p>Currently the documentation for Celix contains information about building and running Celix, as well as some examples.</p>
+ <p class="title">Documentation</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Currently the documentation for Celix contains information about building and running Celix, as well as some examples.</p>
<ul>
<li><a href="/documentation/getting_started.html">Getting Started</a></li>
<li><a href="/documentation/buildingandrunning.html">Building and Running Celix</a></li>
Modified: websites/staging/celix/trunk/content/documentation/buildingandrunning-links.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/buildingandrunning-links.html (original)
+++ websites/staging/celix/trunk/content/documentation/buildingandrunning-links.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
- <h2 id="requirements">Requirements</h2>
+ <p class="title"></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent link">¶</a></h2>
<ul>
<li>CMake (2.8.4 and higher)</li>
<li>GCC (4.2.1)</li>
@@ -139,7 +161,7 @@
<li>CUnit</li>
<li>Celix Source</li>
</ul>
-<h2 id="useful-links">Useful Links</h2>
+<h2 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://www.cmake.org/cmake/help/documentation.html">CMake Documentation</a></li>
</ul>
Modified: websites/staging/celix/trunk/content/documentation/buildingandrunning.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/buildingandrunning.html (original)
+++ websites/staging/celix/trunk/content/documentation/buildingandrunning.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Building and Running</h1>
- <p>Note: Currently there is one build that builds Celix, the dependency manager and several small test bundles. This will be split into several small modules.
+ <p class="title">Building and Running</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Note: Currently there is one build that builds Celix, the dependency manager and several small test bundles. This will be split into several small modules.
Requirements</p>
<p>To be able to build Celix, the following is needed:</p>
<div class="codehilite"><pre>CMake (2.8.4 and higher)
@@ -168,7 +190,7 @@ The following is a list of libraries per
</pre></div>
-<h2 id="building">Building</h2>
+<h2 id="building">Building<a class="headerlink" href="#building" title="Permanent link">¶</a></h2>
<p>Celix uses CMake to generate makefile. There are cmake scripts to build the libraries, but also to deploy created bundles to a named target.
To start building and using Celix these makefiles have to be created. CMake supports out-of-source builds, for Celix the build directory is used for this.</p>
<div class="codehilite"><pre><span class="c1">// First extract the sources</span>
@@ -208,7 +230,7 @@ The following targets are available:
<p>Also it is possible to enter sub directories of the build and run the build from there. So when running make from "build/shell" only the shell
(and dependencies) will be build. This is the same as running "make shell" in the build root.</p>
<p>Note: The build files are recursive. If a target is build, all required dependencies are build (bundles, libraries etc).</p>
-<h2 id="bundles">Bundles</h2>
+<h2 id="bundles">Bundles<a class="headerlink" href="#bundles" title="Permanent link">¶</a></h2>
<p>In Celix a bundle is a library packed in a zip file. A bundle is a top level build target and can be added using the following macro:</p>
<div class="codehilite"><pre><span class="n">bundle</span><span class="p">(</span><span class="o"><</span><span class="n">bundle_name</span><span class="o">></span>
<span class="n">SOURCES</span> <span class="n">source1</span> <span class="n">source2</span> <span class="p">...</span> <span class="n">sourceN</span>
@@ -232,7 +254,7 @@ The given examples are simplified for ba
<p>This can be used to create a package which contains the bundle and additional files (headers etc) needed to use the bundle in different projects.</p>
-<h2 id="targets">Targets</h2>
+<h2 id="targets">Targets<a class="headerlink" href="#targets" title="Permanent link">¶</a></h2>
<p>A named target is used to deploy a group of bundles and create a default configuration file.
To create a target the following command is needed:</p>
<div class="codehilite"><pre><span class="n">deploy</span><span class="p">(</span><span class="o"><</span><span class="n">target_name</span><span class="o">></span> <span class="n">BUNDLES</span> <span class="n">bundle1</span> <span class="n">bundle2</span> <span class="p">...</span> <span class="n">bundleN</span><span class="p">)</span>
@@ -240,7 +262,7 @@ To create a target the following command
<p>A target is deployed to the build directory where the deploy macro is used. So if in <root>/examples a deploy macro is used, the deployment can be found in <root>/<build_root>/examples.</p>
-<h2 id="running">Running</h2>
+<h2 id="running">Running<a class="headerlink" href="#running" title="Permanent link">¶</a></h2>
<p>After building a target, it can be run. To run a target a launcher is needed. This launcher is build as part of the standard Celix build, and is located in build/launcher.
The launcher is a simple executable requiring a configuration file in which required bundles are listed.
If a target is deployed using the "deploy" macro, a configuration file is created by the build system.
@@ -263,7 +285,18 @@ Finally before the launcher can be execu
<div id="download" class="rc">
- <h2 id="requirements">Requirements</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent link">¶</a></h2>
<ul>
<li>CMake (2.8.4 and higher)</li>
<li>GCC (4.2.1)</li>
@@ -272,7 +305,7 @@ Finally before the launcher can be execu
<li>CUnit</li>
<li>Celix Source</li>
</ul>
-<h2 id="useful-links">Useful Links</h2>
+<h2 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://www.cmake.org/cmake/help/documentation.html">CMake Documentation</a></li>
</ul>
Modified: websites/staging/celix/trunk/content/documentation/design.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/design.html (original)
+++ websites/staging/celix/trunk/content/documentation/design.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Celix Design</h1>
- <p>Since Celix tries to follow the OSGi specification as close as possible, most of the design can be found in these
+ <p class="title">Celix Design</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Since Celix tries to follow the OSGi specification as close as possible, most of the design can be found in these
specifications. Some key aspects of OSGi can not be mapped on C, these differences are detailed on this page.</p>
<p>The following important differences are:</p>
<ul>
@@ -140,18 +162,18 @@ specifications. Some key aspects of OSGi
<li><a href="#imported_and_exported_packages">Imported and Exported Packages</a></li>
<li><a href="#exception_handling">Exception Handling</a></li>
</ul>
-<h2 id="services-and-service-interfaces">Services and Service Interfaces</h2>
+<h2 id="services-and-service-interfaces">Services and Service Interfaces<a class="headerlink" href="#services-and-service-interfaces" title="Permanent link">¶</a></h2>
<p>OSGi uses Java Interfaces to define a service. Since C does not have Interfaces as compilable unit, this is not possible
for Celix. To be able to define a service which hides implementation details, Celix uses structs with function pointers.
To register a service, in the activator, the actual functions are assigned to the pointers of the struct. This struct is
registered as service implementation.</p>
-<h2 id="object-and-object-state">Object and Object State</h2>
+<h2 id="object-and-object-state">Object and Object State<a class="headerlink" href="#object-and-object-state" title="Permanent link">¶</a></h2>
<p>Most notably is the use of Objects in Java, and the lack of Objects in C. To solve this and be able to pass instance
data through the framework, structs are used. Every framework method follows the signature as defined in the
specification, with one addition; the first argument is a pointer to a struct instance. The structure of these structs
are hidden behind a typedef to be able to control access to, and to limit/prevent modifications to the struct its data.
So basically the pointer is merely used as a handle to be able to track instances.</p>
-<h2 id="namespaces">Namespaces</h2>
+<h2 id="namespaces">Namespaces<a class="headerlink" href="#namespaces" title="Permanent link">¶</a></h2>
<p>Java uses packages for the namespace of classes, and methods are grouped by class. In C there is no alternative. To
prevent name clashes, function names are prefixed with the name of the class defined in the specification.</p>
<p>Function in C:</p>
@@ -165,7 +187,7 @@ prevent name clashes, function names are
<p>More details about the mapping from Java to C can be found at <a href="/documentation/mapping.html">Mapping</a></p>
-<h2 id="imported-and-exported-packages">Imported and Exported Packages</h2>
+<h2 id="imported-and-exported-packages">Imported and Exported Packages<a class="headerlink" href="#imported-and-exported-packages" title="Permanent link">¶</a></h2>
<p>The OSGi Specification uses packages for importing and exporting service interfaces and additional types. As explained
before, C does not have packages, so it is not possible to export packages. Instead, services are exported and imported.
This implies that the service struct has to be available to the using components.
@@ -173,7 +195,7 @@ There is also no programmatic protection
available, they can be used.
So it is up to the implementer of a service to define the struct and public types separately from the inner types of the
component. The public definitions can be published in a header file.</p>
-<h2 id="exception-handling">Exception Handling</h2>
+<h2 id="exception-handling">Exception Handling<a class="headerlink" href="#exception-handling" title="Permanent link">¶</a></h2>
<p>OSGi uses exceptions to report errors and problems. Celix return a status from every call. This requires that each method
must return an integer which indicates the state. For returned pointers/values (OUT) call-by-reference must be used.</p>
</div>
Modified: websites/staging/celix/trunk/content/documentation/examples.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/examples.html (original)
+++ websites/staging/celix/trunk/content/documentation/examples.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Examples</h1>
- <p>The following examples are available:</p>
+ <p class="title">Examples</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The following examples are available:</p>
<ul>
<li><a href="/examples/helloworld.html">Hello World</a></li>
</ul>
Modified: websites/staging/celix/trunk/content/documentation/getting_started.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/getting_started.html (original)
+++ websites/staging/celix/trunk/content/documentation/getting_started.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,11 +140,22 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
- <h2 id="intro">Intro</h2>
+ <p class="title"></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="intro">Intro<a class="headerlink" href="#intro" title="Permanent link">¶</a></h2>
<p>This page is intended for first time users of Apache Celix. It should guide you through building & installing Apache Celix, setting up a new project, creating your first bundle, setting up the project for use with Eclipse project and finally running and debugging your bundle directly from eclipse workspace. </p>
<p>If there are any uncertainties or question, don't hesitate to ask your questions in the <a href="https://celix.apache.org/support/mailinglist.html">Apache Celix mailing</a>.</p>
-<h2 id="prerequisite">Prerequisite</h2>
+<h2 id="prerequisite">Prerequisite<a class="headerlink" href="#prerequisite" title="Permanent link">¶</a></h2>
<p>Some experience with a command line interface (xterm) is expected to be able to follow this guide. </p>
<p>The following packages (libraries + headers) should be installed on your system:</p>
<ul>
@@ -164,7 +186,7 @@ apt-get install -yq --no-install-recomme
libcurl4-openssl-dev \
cmake
</pre></p>
-<h2 id="building-installing-apache-celix">Building & Installing Apache Celix</h2>
+<h2 id="building-installing-apache-celix">Building & Installing Apache Celix<a class="headerlink" href="#building-installing-apache-celix" title="Permanent link">¶</a></h2>
<p>To get started you first have to install Apache Celix. To do this you can download a source release from the <a href="/download.cgi">download page</a> or checkout the latest version from svn. For this getting started guide the latest trunk version is assumed. Choose a workspace directory to work in and set the environment variable WS to this location. After that, execute the following commands (ignore emtpy lines and lines starting with #):</p>
<div class="codehilite"><pre><span class="c">#Create a new workspace to work in, e.g:</span>
<span class="c">#mkdir ${HOME}/workspace</span>
@@ -192,9 +214,9 @@ apt-get install -yq --no-install-recomme
</pre></div>
-<h2 id="installing-eclipse-cdt">Installing Eclipse CDT</h2>
+<h2 id="installing-eclipse-cdt">Installing Eclipse CDT<a class="headerlink" href="#installing-eclipse-cdt" title="Permanent link">¶</a></h2>
<p>Download the latest eclipse CDT at <a href="http://www.eclipse.org">http://www.eclipse.org</a> and install it on your system. For more information on how the install eclipse on your system consult the eclipse documentation. For this getting started guide the luna version of eclipse was used (<a href="http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/luna/R/eclipse-cpp-luna-R-linux-gtk-x86_64.tar.gz">linux</a> <a href="http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/luna/R/eclipse-cpp-luna-R-macosx-cocoa-x86_64.tar.gz">mac</a>).</p>
-<h2 id="apache-celix-bundle-project">Apache Celix Bundle project</h2>
+<h2 id="apache-celix-bundle-project">Apache Celix Bundle project<a class="headerlink" href="#apache-celix-bundle-project" title="Permanent link">¶</a></h2>
<p>Now that Apache Celix and Eclipse is installed, we are ready to create a new Apache Celix Bundle project. In this project cmake will be create a singe hello world bundle with a deployment configuration for testing the bundle.</p>
<p>For Apache Celix and an Apache Celix Bundle project CMake is used as build system. CMake is a cross platform build. This getting started guide will only shows a small part of CMake, for a more detailed introduction on CMake consult the <a href="http://www.cmake.org/documentation">CMake documentation</a>. </p>
<p>The installation of Apache Celix, added additional CMake files to extend the default functionality of CMake in order to support the creating and testing of Apache Celix Bundles. </p>
@@ -308,7 +330,7 @@ cd <span class="cp">${</span><span class
</pre></div>
-<h3 id="building">Building</h3>
+<h3 id="building">Building<a class="headerlink" href="#building" title="Permanent link">¶</a></h3>
<p>One of the highly recommended features of CMake is the ability to do out of source builds, the benefit is that all of the build results will go in a seperate directory without cluttering the (source) project. To create the build directory and build the project execute the following commands:</p>
<div class="codehilite"><pre>cd <span class="cp">${</span><span class="n">WS</span><span class="cp">}</span>
mkdir myproject-build
@@ -319,13 +341,11 @@ make all
<p>Hopefully you will some some build results scrolling over the screen and actual build results in the build directory. There should be a hello_world.zip in the bundles/hello_world directory, this the actual bundle. But a bundle on its own has no real value, so lets setup a deployment and run the Apache Celix framwork with this bundle.</p>
-<h3 id="running">Running</h3>
+<h3 id="running">Running<a class="headerlink" href="#running" title="Permanent link">¶</a></h3>
<p>To create a deployment for the hello_world bundle two things are needed: </p>
<ol>
<li>Add a <code>deploy.cmake</code> in the <code>bundles/hello_world</code> dir declaring what to deploy and under which name.</li>
-<li>
-<p>Append the deploy_targets() marco call to the end of the root <code>CMakeLists.txt</code> file (<code>${WS}/myproject/CMakeLists.txt</code>). This marcro will look for deploy.cmake files, parse them and when make is runned create the actual deployment structure. </p>
-<div class="codehilite"><pre><span class="cp">${</span><span class="n">WS</span><span class="cp">}</span>/myproject/bundles/hello_world/deploy.cmake
+<li>Append the deploy_targets() marco call to the end of the root <code>CMakeLists.txt</code> file (<code>${WS}/myproject/CMakeLists.txt</code>). This marcro will look for deploy.cmake files, parse them and when make is runned create the actual deployment structure. <div class="codehilite"><pre><span class="cp">${</span><span class="n">WS</span><span class="cp">}</span>/myproject/bundles/hello_world/deploy.cmake
deploy("myproject" BUNDLES
<span class="cp">${</span><span class="n">CELIX_BUNDLES_DIR</span><span class="cp">}</span>/shell.zip
<span class="cp">${</span><span class="n">CELIX_BUNDLES_DIR</span><span class="cp">}</span>/shell_tui.zip
@@ -356,7 +376,7 @@ sh run.sh
</pre></div>
-<h2 id="apache-celix-bundle-project-in-eclipse">Apache Celix Bundle Project in Eclipse</h2>
+<h2 id="apache-celix-bundle-project-in-eclipse">Apache Celix Bundle Project in Eclipse<a class="headerlink" href="#apache-celix-bundle-project-in-eclipse" title="Permanent link">¶</a></h2>
<p>A nice feature of CMake is the ability to generate Eclipse project files, with this feature bundles can also be developed with use of Eclipse. This should help speed up the development process.
To get started change directory to the build directory and generate a eclipse project file.</p>
<div class="codehilite"><pre>cd <span class="cp">${</span><span class="n">WS</span><span class="cp">}</span>/myproject-build
Modified: websites/staging/celix/trunk/content/documentation/mapping.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/mapping.html (original)
+++ websites/staging/celix/trunk/content/documentation/mapping.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,10 +140,21 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Mapping</h1>
- <p>To be able to follow the OSGi specification, a standard mapping from C to Java is defined. This mapping
+ <p class="title">Mapping</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>To be able to follow the OSGi specification, a standard mapping from C to Java is defined. This mapping
takes care of how instances, parameters, return values and error codes are used.</p>
-<h2 id="example">Example</h2>
+<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h2>
<p>Before going into detail, here is an example of the mapping from a method in Java to a function in C:</p>
<div class="codehilite"><pre><span class="n">celix_status_t</span> <span class="n">bundleContext_getServiceReferences</span><span class="p">(</span><span class="n">BUNDLE_CONTEXT</span> <span class="n">context</span><span class="p">,</span> <span class="k">const</span> <span class="kt">char</span> <span class="o">*</span> <span class="n">serviceName</span><span class="p">,</span> <span class="kt">char</span> <span class="o">*</span> <span class="n">filter</span><span class="p">,</span> <span class="n">ARRAY_LIST</span> <span class="o">*</span><span class="n">service_references</span><span class="p">)</span>
@@ -141,7 +163,7 @@ takes care of how instances, parameters,
</pre></div>
-<h2 id="template">Template</h2>
+<h2 id="template">Template<a class="headerlink" href="#template" title="Permanent link">¶</a></h2>
<p>Using the provided example, the following template can be extracted:</p>
<div class="codehilite"><pre><span class="cm">/**</span>
<span class="cm"> * celix_status_t: return type of the status code</span>
@@ -158,7 +180,7 @@ takes care of how instances, parameters,
</pre></div>
-<h2 id="details">Details</h2>
+<h2 id="details">Details<a class="headerlink" href="#details" title="Permanent link">¶</a></h2>
<p>To fully explain the mapping, the following items will be detailed:</p>
<ul>
<li>Instance parameter</li>
@@ -166,22 +188,22 @@ takes care of how instances, parameters,
<li>Output parameters</li>
<li>Memory pools</li>
</ul>
-<h3 id="instances">Instances</h3>
+<h3 id="instances">Instances<a class="headerlink" href="#instances" title="Permanent link">¶</a></h3>
<p>When using Java, methods are related to an instance of a type. So for example, when the "getServiceReferences" method is used,
it is always executed on an instance of BundleContext.
When using C, functions are not related to any type, and as such, no instance information is available. To make this possible
in Celix a pointer to the needed instance is always passed as first argument. The only exception are the "create" functions, they
are used to create a new instance.</p>
<p>Furthermore, the instance typename is used as part of the function name, see "design.html" for more information.</p>
-<h3 id="error-codes">Error codes</h3>
+<h3 id="error-codes">Error codes<a class="headerlink" href="#error-codes" title="Permanent link">¶</a></h3>
<p>The OSGi specification uses Java Exceptions for error handling. Even though there are Exceptions-like solutions for C, Celix uses
the simpler approach. Every method in Celix returns an status code (celix_status_t), this code can be used for error handling.</p>
-<h3 id="output-parameters">Output parameters</h3>
+<h3 id="output-parameters">Output parameters<a class="headerlink" href="#output-parameters" title="Permanent link">¶</a></h3>
<p>Since the return value is always used for the status code output parameters are used to get a possible result from a function.
Celix uses pass-by-reference for this, the uses has to supply a pointer to the function to get the results. Using this mechanism it is
also possible to use multiple output parameters.
Celix always uses the last parameter(s) for output, and the caller has to NULL-initialize the result field.</p>
-<h3 id="memory-pools">Memory pools</h3>
+<h3 id="memory-pools">Memory pools<a class="headerlink" href="#memory-pools" title="Permanent link">¶</a></h3>
<p>Celix uses APR memory pools for allocation. In the case a functions result has to be allocated to the caller its own pool, the pool has
to be supplied as an parameter. Note: Not all of Celix' API have been updated to use APR (and memory pools), this is a work in progress.</p>
</div>
Modified: websites/staging/celix/trunk/content/documentation/memorypools.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/memorypools.html (original)
+++ websites/staging/celix/trunk/content/documentation/memorypools.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title">Memory Pools</h1>
- <p>Celix uses the <a href="http://apr.apache.org">Apache Portable Runtime</a> (APR) as abstraction layer for platforms. APR uses memory pools to make memory management easier. To be able to use memory pools the lifetime of "objects" must be known.</p>
+ <p class="title">Memory Pools</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Celix uses the <a href="http://apr.apache.org">Apache Portable Runtime</a> (APR) as abstraction layer for platforms. APR uses memory pools to make memory management easier. To be able to use memory pools the lifetime of "objects" must be known.</p>
<p>This page details how Celix user APR memory pools and what the lifetime of objects within Celix is. This will result in some best practices that should be followed when using APR.</p>
<p>Roughly, within Celix, the following object groups can be identified, where each object has its own memory pool:</p>
<ul>
Modified: websites/staging/celix/trunk/content/documentation/releasing-links.html
==============================================================================
--- websites/staging/celix/trunk/content/documentation/releasing-links.html (original)
+++ websites/staging/celix/trunk/content/documentation/releasing-links.html Wed Jul 8 12:47:33 2015
@@ -60,7 +60,18 @@
<a href="/index.html"><img id="headerimage" src="/images/celix.png" alt="Apache Celix"
height="130px"></a>
<div id="navbar">
- <ul>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/celix.html">About</a><ul>
<li><a href="/celix.html">Celix</a></li>
@@ -129,8 +140,19 @@
<div id="main">
<div id="homecenter">
<div id="homeleft">
- <h1 class="title"></h1>
- <h2 id="requirements">Requirements</h2>
+ <p class="title"></p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent link">¶</a></h2>
<ul>
<li>CMake (2.8.4)</li>
<li>GCC (4.2.1)</li>
@@ -139,7 +161,7 @@
<li>CUnit</li>
<li>Celix Source</li>
</ul>
-<h2 id="useful-links">Useful Links</h2>
+<h2 id="useful-links">Useful Links<a class="headerlink" href="#useful-links" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://www.cmake.org/cmake/help/documentation.html">CMake Documentation</a></li>
</ul>