You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@felix.apache.org by bu...@apache.org on 2015/09/01 08:05:20 UTC
svn commit: r963800 [1/16] - in /websites/staging/felix/trunk/content: ./
documentation/ documentation/community/ documentation/development/
documentation/faqs/ documentation/subprojects/
documentation/subprojects/apache-felix-commons/ documentation/su...
Author: buildbot
Date: Tue Sep 1 06:05:17 2015
New Revision: 963800
Log:
Staging update by buildbot for felix
Modified:
websites/staging/felix/trunk/content/ (props changed)
websites/staging/felix/trunk/content/documentation.html
websites/staging/felix/trunk/content/documentation/community.html
websites/staging/felix/trunk/content/documentation/community/apache-felix-community-roles-and-processes.html
websites/staging/felix/trunk/content/documentation/community/contributing-source-code.html
websites/staging/felix/trunk/content/documentation/community/contributing.html
websites/staging/felix/trunk/content/documentation/community/felix-r4-contributions.html
websites/staging/felix/trunk/content/documentation/community/projects-using-felix.html
websites/staging/felix/trunk/content/documentation/development.html
websites/staging/felix/trunk/content/documentation/development/bnd-testing-harness.html
websites/staging/felix/trunk/content/documentation/development/building-felix.html
websites/staging/felix/trunk/content/documentation/development/coding-standards.html
websites/staging/felix/trunk/content/documentation/development/dependencies-file-template.html
websites/staging/felix/trunk/content/documentation/development/dependencies.html
websites/staging/felix/trunk/content/documentation/development/integrating-felix-with-eclipse.html
websites/staging/felix/trunk/content/documentation/development/integrating-felix-with-netbeans.html
websites/staging/felix/trunk/content/documentation/development/issue-tracking.html
websites/staging/felix/trunk/content/documentation/development/roadmap.html
websites/staging/felix/trunk/content/documentation/development/source-code.html
websites/staging/felix/trunk/content/documentation/development/svn-repository-structure.html
websites/staging/felix/trunk/content/documentation/faqs.html
websites/staging/felix/trunk/content/documentation/faqs/apache-felix-bundle-plugin-faq.html
websites/staging/felix/trunk/content/documentation/getting-started.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-autoconf.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-commons/creating-bundles-using-bnd.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-deployment-admin.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-file-install.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework-security.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-alternative-java-vms.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-google-android.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-bundle-cache.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-faq.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-launching-and-embedding.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-2-ct-results.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-3-ct-results.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-gogo/rfc-147-overview.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/dive-into-the-ipojo-manipulation-depths.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-use-ipojo-manipulation-metadata.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-write-your-own-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-eclipse-integration.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-feature-overview.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/apache-felix-ipojo-dosgi.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/how-to-use-ipojo-annotations.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-advanced-tutorial.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-composition-tutorial.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-hello-word-maven-based-tutorial.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-in-10-minutes.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-architecture.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-maven.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-methods.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-tutorial.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-keypoints.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedvms.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-testing-components.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/apache-felix-ipojo-online-manipulator.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-arch-command.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-karaf-feature.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/junit4osgi.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/apache-felix-ipojo-api.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/apache-felix-ipojo-instances.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/architecture-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/configuration-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/controller-lifecycle-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/event-admin-handlers.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/extender-pattern-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/injecting-bundle-context.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/ipojo-jmx-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/lifecycle-callback-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/temporal-service-dependency.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/white-board-pattern-handler.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/instance-vs-service-controller.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/combining-ipojo-and-configuration-admin.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/constructing-pojo-objects-with-factory-methods.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/how-to-use-ipojo-factories.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-hierarchical-composition-overview.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-ipojo-introspection-api.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-stereotypes.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/using-xml-schemas.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-why-choose-ipojo.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/articles-and-presentations.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/download.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-reference-card.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-support.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-ipojo/related-works.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-lightweight-http-service.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-log.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-manifest-generator-mangen.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-obr-plugin.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-osgi-plugin.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-metatype-service.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-osgi-bundle-repository.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-osgi-core.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-preferences-service.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-remote-shell.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-serialization-framework.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-shell-tui.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-shell.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-contributing.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features/apache-felix-sigil-eclipse.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features/apache-felix-sigil-eclipse/apache-felix-sigil-eclipse-features.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-road-map.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-installation.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-quickstart.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-settings.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-junit.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-projects.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-properties.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-filesystem.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-obr.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-acknowledgments.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-driver-architecture.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-getting-started.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-known-issues.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples/upnp-writing-cd-and-cp.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-background.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-file-store.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-getting-started.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-introduction.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-mongodb-store.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/branding-the-web-console.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/providing-resources.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/providing-web-console-plugins.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/web-console-logging.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/web-console-output-templating.html
websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-web-console/web-console-security-provider.html
websites/staging/felix/trunk/content/documentation/subprojects/mosgi-managed-osgi-framework.html
websites/staging/felix/trunk/content/documentation/subprojects/mosgi-managed-osgi-framework/probeguide.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-application-demonstration.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-1.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-2.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-2b.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-3.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-4.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-5.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-6.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-7.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-8.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/checking-out-and-building-felix-with-netbeans.html
websites/staging/felix/trunk/content/documentation/tutorials-examples-and-presentations/presentations.html
websites/staging/felix/trunk/content/index.html
websites/staging/felix/trunk/content/links.html
websites/staging/felix/trunk/content/media.html
websites/staging/felix/trunk/content/miscellaneous.html
websites/staging/felix/trunk/content/miscellaneous/apache-karaf.html
websites/staging/felix/trunk/content/miscellaneous/board-reports.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/apache-felix-board-report-template.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2007-04.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2007-05.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2007-06.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2007-09.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2007-12.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2008-03.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2008-06.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2008-09.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2008-12.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2009-03.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2009-06.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2009-09.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2009-12.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2010-03.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2010-06.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2010-09.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2010-12.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2011-03.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2011-06.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2011-09.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2011-12.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2012-03.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2012-06.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2012-09.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2012-12.html
websites/staging/felix/trunk/content/miscellaneous/board-reports/board-report-2013-03.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-001-use-cases.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-002-profiles.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-002-profiles/cat-scan-002-001-basic-profile.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-003-run-log-archive.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-004-api-reference.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-005-technical-compatibility-kit.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-006-glossary.html
websites/staging/felix/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-007-references.html
websites/staging/felix/trunk/content/miscellaneous/incubator-status-report-january-2007.html
websites/staging/felix/trunk/content/miscellaneous/incubator-status-report-october-2006.html
websites/staging/felix/trunk/content/miscellaneous/osgi-bundle-service-diagrams.html
websites/staging/felix/trunk/content/miscellaneous/sandbox.html
websites/staging/felix/trunk/content/miscellaneous/sandbox/composite-bundles.html
websites/staging/felix/trunk/content/miscellaneous/sandbox/virtual-bundles.html
websites/staging/felix/trunk/content/miscellaneous/sandbox/web-console-ng.html
websites/staging/felix/trunk/content/miscellaneous/subproject-release-status.html
websites/staging/felix/trunk/content/miscellaneous/tlp-task-list.html
Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 1 06:05:17 2015
@@ -1 +1 @@
-1700161
+1700393
Modified: websites/staging/felix/trunk/content/documentation.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation.html (original)
+++ websites/staging/felix/trunk/content/documentation.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,30 +77,17 @@
</div>
<h1>Documentation</h1>
- <p><em>The Felix web site and documentation are managed with the <a href="https://www.apache.org/dev/cms.html">Apache CMS</a>.
-For Apache Felix specific extensions see the <a href="#site-how-to">Site How-To</a>
-section below.</em></p>
-<div class="info">
-<p>
-The Felix site is being converted from a Confluence exported site to an
-Apache CMS managed site. During this conversion not all pages will display
-correctly. All non-fully converted pages will show a tip box pointing to
-the original Confluence exported page for reference.
-</p>
-
-<p>
-Once migration of a page has completed the <code>translation_pending</code>
-header should be removed from the page source. After that the tip box will not be
-shown any more.
-</p>
-
-<p>
-While this page has technically been translated already, the <code>translation-pending</code>
-header is kept to remind us to remove this info box once translation has
-completed.
-</p>
-</div>
-
+ <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>In an effort to make it easier to find desired documentation, we have divided our documentation section into the following six areas:</p>
<ul>
<li><a href="/documentation/getting-started.html">Getting started</a> - This area captures a few links from the areas below that will help you get started with Felix.</li>
@@ -102,7 +100,10 @@ completed.
<p>In addition a <a href="">site map</a> is available as a table of
contents of the site.</p>
<p>If you are unable to find the documentation you need, please ask on the <a href="/mailinglists.html">mailing lists</a>. Also, feedback on improving the documentation and/or organization of this site is welcome.</p>
-<h2 id="books">Books</h2>
+<p><em>The Felix web site and documentation are managed with the <a href="https://www.apache.org/dev/cms.html">Apache CMS</a>.
+For Apache Felix specific extensions see the <a href="#site-how-to">Site How-To</a>
+section below.</em></p>
+<h2 id="books">Books<a class="headerlink" href="#books" title="Permanent link">¶</a></h2>
<p>The most important "books" on OSGi are of course the specifications themselves. They are quite a good read but are also complete and contain stuff, you might be interested
in. So for a starter you might interested to read the following:</p>
<ul>
@@ -130,10 +131,10 @@ Many OSGi core concepts are greatly expl
<li><a href="http://www.manning.com/cogoluegnes/">Spring Dynamic Modules in Action</a>; Arnaud Cogoluègnes, Thierry Templier, Andy Piper; Manning, 2010</li>
<li><a href="http://shop.oreilly.com/product/0636920028086.do#">Building Modular Cloud Apps with OSGi</a>; Paul Bakker, Bert Ertman; O'Reilly, 2013. Uses Apache Felix. For experienced Java developers in the enterprise, this practical, hands-on book shows you how to use OSGi to design, develop, and deploy modular cloud applications. </li>
</ul>
-<h2 id="site-how-to">Site How-To</h2>
+<h2 id="site-how-to">Site How-To<a class="headerlink" href="#site-how-to" title="Permanent link">¶</a></h2>
<p>The site is managed with the <a href="https://www.apache.org/dev/cms.html">Apache CMS</a>
where the source is kept in SVN at <a href="https://svn.apache.org/repos/asf/felix/site/trunk/content">https://svn.apache.org/repos/asf/felix/site/trunk/content</a>.</p>
-<h3 id="to-update-the-documentation-using-the-cms-system">To update the documentation using the CMS system</h3>
+<h3 id="to-update-the-documentation-using-the-cms-system">To update the documentation using the CMS system<a class="headerlink" href="#to-update-the-documentation-using-the-cms-system" title="Permanent link">¶</a></h3>
<ul>
<li>Install the bookmarklet from the <a href="https://cms.apache.org/">cms</a> page. You only have to do this once.</li>
<li>Navigate to the page you wish to edit (on the live site, not in the cms).</li>
@@ -147,7 +148,7 @@ where the source is kept in SVN at <a hr
</ul>
<p>There is also a <a href="https://www.apache.org/dev/cmsref.html">Reference Manual</a> of the Apache CMS as well as a
video tutorial at <a href="http://s.apache.org/cms-tutorial">http://s.apache.org/cms-tutorial</a>.</p>
-<h3 id="features-of-the-apache-felix-site">Features of the Apache Felix Site</h3>
+<h3 id="features-of-the-apache-felix-site">Features of the Apache Felix Site<a class="headerlink" href="#features-of-the-apache-felix-site" title="Permanent link">¶</a></h3>
<p>This section lists some Apache Felix features to help with the maintenance
of the site, such as automatic link generation.</p>
<p>Start the file with a <code>Title:</code> line to define the page title and the first H1 tag:</p>
@@ -234,18 +235,18 @@ It is important to have the first part a
the Django/Markdown combo will create a list for each entry.
</div>
-<h3 id="code-highlighting">Code Highlighting</h3>
+<h3 id="code-highlighting">Code Highlighting<a class="headerlink" href="#code-highlighting" title="Permanent link">¶</a></h3>
<p>Code Highlighting works by indenting code by four blanks. To indicate the
type of highlighting preced the code style text with either <code>:::<lexer></code> to
get high lighted code using the given <code><lexer></code> or <code>#!<lexer></code> to get high
lighted code with line numbers using the given <code><lexer></code>. See
<a href="http://www.apache.org/dev/cmsref.html#code-hilighter">http://www.apache.org/dev/cmsref.html#code-hilighter</a> for main info and
<a href="http://pygments.org/docs/lexers/">http://pygments.org/docs/lexers/</a> for supported lexers</p>
-<h3 id="html-and-markdown">HTML and Markdown</h3>
+<h3 id="html-and-markdown">HTML and Markdown<a class="headerlink" href="#html-and-markdown" title="Permanent link">¶</a></h3>
<p>Markdown supports embedding HTML. But be aware that contents of HTML elements
are not further handled by the Markdown converter. Thus it is not possible
to embed Markdown syntax inside of HTML elements to have them converted.</p>
-<h3 id="manual-generation">Manual Generation</h3>
+<h3 id="manual-generation">Manual Generation<a class="headerlink" href="#manual-generation" title="Permanent link">¶</a></h3>
<p>When commiting changes to pages into SVN the pages are automatically
generated in <a href="http://felix.staging.apache.org">the staging site</a>.</p>
<div class="info">
@@ -281,7 +282,7 @@ and <code>build_file.pl</code> scripts t
<p>The argument to the <code>--source</code> parameter is relative to the <code>--source-base</code> folder.</p>
-<h3 id="configuring-site-generation-on-mac">Configuring site generation on Mac</h3>
+<h3 id="configuring-site-generation-on-mac">Configuring site generation on Mac<a class="headerlink" href="#configuring-site-generation-on-mac" title="Permanent link">¶</a></h3>
<div class="info">
Those instructions were computed on Mountain Lion.
</div>
@@ -313,7 +314,7 @@ Those instructions were computed on Moun
<div class="codehilite"><pre>tools/build/build_site.pl --source-base <span class="nv">$PWD</span>/trunk --target-base <span class="nv">$PWD</span>/trunk/target
</pre></div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1541842 by marrs on Thu, 14 Nov 2013 07:48:16 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/community.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/community.html (original)
+++ websites/staging/felix/trunk/content/documentation/community.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,7 +77,18 @@
</div>
<h1>Community Documentation</h1>
- <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="/documentation/community/apache-felix-community-roles-and-processes.html">Apache Felix Community Roles and Processes</a></li>
<li><a href="/documentation/community/contributing.html">Contributing</a></li>
<li><a href="/documentation/community/contributing-source-code.html">Contributing Source Code</a></li>
@@ -74,7 +96,7 @@
<li><a href="/documentation/community/projects-using-felix.html">Projects Using Felix</a></li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/community/apache-felix-community-roles-and-processes.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/community/apache-felix-community-roles-and-processes.html (original)
+++ websites/staging/felix/trunk/content/documentation/community/apache-felix-community-roles-and-processes.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,29 +77,40 @@
</div>
<h1>Apache Felix Community Roles and Processes</h1>
- <h1 id="roles">Roles</h1>
+ <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>
+<h1 id="roles">Roles<a class="headerlink" href="#roles" title="Permanent link">¶</a></h1>
<p>There are different roles with which Felix community members may be associated, these roles are: users, contributors, committers, and Project Management Committee (PMC) members. These roles are assigned and assumed based on merit. Everyone in the Felix community can participate to whatever level they desire, but participating and the resulting merit gained is directly linked to the role an individual may obtain.</p>
-<h2 id="users">Users</h2>
+<h2 id="users">Users<a class="headerlink" href="#users" title="Permanent link">¶</a></h2>
<p>Users are the people who use any of the products of the Felix project. People in this role are not contributing code, but they are using the products, reporting bugs, making feature requests, testing code, and such. This is by far the most important category of people, since without users there is no reason for Felix. When a user starts to contribute code or documentation patches, they become a <em>Contributor</em>.</p>
-<h2 id="contributors">Contributors</h2>
+<h2 id="contributors">Contributors<a class="headerlink" href="#contributors" title="Permanent link">¶</a></h2>
<p>Contributors are the people who write code or documentation patches or contribute positively to the project in other ways. A volunteer's contribution is always recognized.</p>
-<h2 id="committers">Committers</h2>
+<h2 id="committers">Committers<a class="headerlink" href="#committers" title="Permanent link">¶</a></h2>
<p>Contributors who give frequent and valuable contributions to a subproject of Felix can have their status promoted to that of a <em>Committer</em>. A Committer has write access to Felix' source code repository.</p>
-<h2 id="pmc-members">PMC Members</h2>
+<h2 id="pmc-members">PMC Members<a class="headerlink" href="#pmc-members" title="Permanent link">¶</a></h2>
<p>Committers who frequently participate with valuable contributions may have their status promoted to that of a <em>PMC member</em>. This committee is the official managing body of project and is responsible for setting its overall direction.</p>
-<h1 id="processes">Processes</h1>
-<h2 id="becoming-a-user-or-contributor">Becoming a User or Contributor</h2>
+<h1 id="processes">Processes<a class="headerlink" href="#processes" title="Permanent link">¶</a></h1>
+<h2 id="becoming-a-user-or-contributor">Becoming a User or Contributor<a class="headerlink" href="#becoming-a-user-or-contributor" title="Permanent link">¶</a></h2>
<p>There is no requirement for becoming a User or Contributor; these roles are open to everyone.</p>
-<h2 id="becoming-a-committer">Becoming a Committer</h2>
+<h2 id="becoming-a-committer">Becoming a Committer<a class="headerlink" href="#becoming-a-committer" title="Permanent link">¶</a></h2>
<p>In order for a Contributor to become a Committer, another Committer can nominate that Contributor to the PMC. Once a Contributor is nominated, the PMC will call a vote on the PMC mailing list and if there are at least 3 positive votes and no negative votes after three days, then the Contributor is accepted as a Committer. The Contributor should not be consulted about his/her desire to become a Committer before the vote or be informed that they are being considered, since this could create hard feelings if the vote does not pass.</p>
<p>Upon a positive vote result, the Contributor will be emailed by the PMC to invite him/her to become a Committer. If the invitation is accepted, an announcement about the new Committer is made to the developer mailing list and he/she is given write access to the source code repository. A Contributor will not officially become a Committer until the appropriate legal paperwork is submitted.</p>
-<h2 id="becoming-a-pmc-member">Becoming a PMC Member</h2>
+<h2 id="becoming-a-pmc-member">Becoming a PMC Member<a class="headerlink" href="#becoming-a-pmc-member" title="Permanent link">¶</a></h2>
<p>In order to become a PMC member, another PMC member must nominate the Committer. Once the Committer is nominated, the PMC will call a vote on the PMC mailing list and if there are at least 3 positive votes and no negative votes after three days, then the Committer is accepted as a PMC member. The Committer should not be consulted about his/her desire to become a PMC member before the vote or be informed that they are being considered, since this could create hard feelings if the vote does not pass.</p>
<p>Upon a positive vote result, the Committer will be emailed by the PMC to invite him/her to become a PMC member. If the invitation is accepted, an announcement about the new PMC member is made to the developer mailing list.</p>
-<h3 id="exceptions">Exceptions</h3>
+<h3 id="exceptions">Exceptions<a class="headerlink" href="#exceptions" title="Permanent link">¶</a></h3>
<p>It is not strictly necessary to be a Committer first in order to become a PMC member. In some cases, the PMC may feel that an individual may offer needed management expertise to the project. Such individuals can be nominated by PMC members. Any such newly accepted PMC members will also be given Committer status.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/community/contributing-source-code.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/community/contributing-source-code.html (original)
+++ websites/staging/felix/trunk/content/documentation/community/contributing-source-code.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,9 +77,20 @@
</div>
<h1>Contributing Source Code</h1>
- <h1 id="source-code-contributions">Source Code Contributions</h1>
+ <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>
+<h1 id="source-code-contributions">Source Code Contributions<a class="headerlink" href="#source-code-contributions" title="Permanent link">¶</a></h1>
<p>Source code contributions fall into two categories: patches or grants. This document describes both and how to handle each.</p>
-<h2 id="patches">Patches</h2>
+<h2 id="patches">Patches<a class="headerlink" href="#patches" title="Permanent link">¶</a></h2>
<p>A patch is a small change to existing code, typically in response to a bug fix or improvement. If you have created a patch, you should:</p>
<ol>
<li>Create a <a href="http://issues.apache.org/jira/browse/Felix">JIRA</a> issue (or find a pertinent existing issue) describing the issue needing to be addressed.</li>
@@ -77,7 +99,7 @@
<li>The patch will eventually be reviewed and applied (if accepted) by a Felix committer, but feel free to bug us [nicely]() if you get impatient.</li>
</ol>
<p>Providing patches is a very good way to become a committer at Felix, since we'd rather have you review and apply the patches than us. :-)</p>
-<h2 id="grants">Grants</h2>
+<h2 id="grants">Grants<a class="headerlink" href="#grants" title="Permanent link">¶</a></h2>
<p>A grant involves donating a larger chunk of code developed elsewhere. The line dividing a patch and a grant is sort of like the definition of pornography, we know it when we see it. The steps for granting software are a little more complicated since we need to ensure proper IP handling. For grants, you should:</p>
<ol>
<li>Verify that you have the authorization to donate the code.</li>
@@ -92,7 +114,7 @@
</ol>
<p>Granting code is also a path to committership at Felix, since we look more highly on contributions from developers who wish to stay involved in the continuing evolution and maintenance of the donated code.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/community/contributing.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/community/contributing.html (original)
+++ websites/staging/felix/trunk/content/documentation/community/contributing.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,23 +77,34 @@
</div>
<h1>Contributing</h1>
- <h1 id="contributing">Contributing</h1>
+ <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>
+<h1 id="contributing">Contributing<a class="headerlink" href="#contributing" title="Permanent link">¶</a></h1>
<p>Apache Felix is a volunteer effort, so there is always plenty of work that needs to be accomplished. If you want to help support Felix, this page is intended as a starting point for specific contribution ideas. To further understand how the Felix community operates, refer to the <a href="/documentation/community/apache-felix-community-roles-and-processes.html">Community Roles and Processes</a> document and/or join the [mailing lists|mailinglists].</p>
<p>The Felix project organizes its "to do" list using the <a href="http://issues.apache.org/jira/browse/Felix">JIRA</a> issue tracking system. Specific items from Felix' JIRA issue tracking system are highlighted on this page, but are not limited to it. The purpose of the list here is to highlight issues that are either more important or serve as good entry points for new contributors.</p>
<p>It is important to point out that you do not need to be a programmer to contribute to Felix. As such, we will break out the list of issues below for non-programmers and programmers.</p>
-<h2 id="non-programmers">Non-Programmers</h2>
+<h2 id="non-programmers">Non-Programmers<a class="headerlink" href="#non-programmers" title="Permanent link">¶</a></h2>
<ul>
<li>Improve web site or documentation (e.g., create/propose FAQ entries). There is no specific JIRA issue for this task, but any contributions could be posted as new JIRA issues for the <a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12310100&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12312255">Documentation</a> component.</li>
<li>Define a compatibility documentation legend for bundle subprojects. <a href="http://issues.apache.org/jira/browse/FELIX-537">FELIX-537</a></li>
</ul>
-<h2 id="programmers">Programmers</h2>
+<h2 id="programmers">Programmers<a class="headerlink" href="#programmers" title="Permanent link">¶</a></h2>
<ul>
<li>Write tests for the framework and/or its sub-projects, either using JUnit or the new <a href="http://felix.apache.org/site/bnd-testing-harness.html">BND testing harness</a></li>
<li>Work on an installer that can install Felix as a daemon/service. <a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12310100&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12310803">Installer issues</a></li>
<li>Browse issues in <a href="http://issues.apache.org/jira/browse/Felix">JIRA</a> and submit a patch.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/community/felix-r4-contributions.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/community/felix-r4-contributions.html (original)
+++ websites/staging/felix/trunk/content/documentation/community/felix-r4-contributions.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,10 +77,32 @@
</div>
<h1>Felix R4 contributions</h1>
- <h1 id="felix-r4-osgi-service-platform-contributions">Felix R4 OSGi Service Platform Contributions</h1>
+ <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>
+<h1 id="felix-r4-osgi-service-platform-contributions">Felix R4 OSGi Service Platform Contributions<a class="headerlink" href="#felix-r4-osgi-service-platform-contributions" title="Permanent link">¶</a></h1>
<p>These are the recorded contributions:</p>
-<p>| org.osgi.framework | The OSGi Framework Package. | Richard Hall (LSR/UJF) | Project contribution | ICLA, CCLA, and Grant | Yes |
-| org.osgi.service.cm | The OSGi Configuration Admin service Package. | Felix Meschberger | <a href="http://mail-archives.apache.org/mod_mbox/incubator-felix-dev/200704.mbox/%3c46167210.9080109@ungoverned.org%3e">Result</a> | Grant and ICLA | Yes |</p>
+<table class="table">
+<thead>
+<tr>
+<th>org.osgi.framework</th>
+<th>The OSGi Framework Package.</th>
+<th>Richard Hall (LSR/UJF)</th>
+<th>Project contribution</th>
+<th>ICLA, CCLA, and Grant</th>
+<th>Yes</th>
+</tr>
+</thead>
+<tbody></tbody>
+</table>
<p>| org.osgi.service.device | The OSGi Device Access Package. | | | | |</p>
<p>| org.osgi.service.io | The OSGi IO Connector Specification Version 1.0. | Pending, To Be Announced | | | |</p>
<p>| org.osgi.service.metatype | The OSGi Metatype Package. | Felix Meschberger | <a href="http://mail-archives.apache.org/mod_mbox/incubator-felix-dev/200704.mbox/%3c46167210.9080109@ungoverned.org%3e">Result</a> | Grant and ICLA | Yes |</p>
@@ -81,7 +114,7 @@
<p>| org.apache.felix.shell.remote | Remote Shell | Dieter Wimberger | <a href="http://markmail.org/message/k2yd6zsrsifloelp">Result</a> | [IP Clearance|http://incubator.apache.org/ip-clearance/felix-remote-shell.html] | Yes |</p>
<p>Send comments to the <a href="/mailinglists.html">Felix developers mailinglist</a>.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/community/projects-using-felix.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/community/projects-using-felix.html (original)
+++ websites/staging/felix/trunk/content/documentation/community/projects-using-felix.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,7 +77,18 @@
</div>
<h1>Projects Using Felix</h1>
- <p>This page highlights projects that use Apache Felix (listed alphabetically):</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>This page highlights projects that use Apache Felix (listed alphabetically):</p>
<ul>
<li><a href="http://karaf.apache.org">Apache Karaf</a> - A small, OSGi-based runtime that provides a lightweight container into which various components and applications can be deployed (formerly an Apache Felix subproject).</li>
<li><a href="http://servicemix.apache.org/">Apache ServiceMix</a> - an Enterprise Service Bus (using Felix via Karaf).</li>
@@ -79,7 +101,7 @@
<li><a href="https://sip-communicator.dev.java.net/">SIP Communicator</a> - a multi-protocol instant messenger and SIP software phone.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/development.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/development.html (original)
+++ websites/staging/felix/trunk/content/documentation/development.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,7 +77,18 @@
</div>
<h1>Development</h1>
- <h1 id="development">Development</h1>
+ <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>
+<h1 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h1>
<p>This page contains links related to Felix project development.</p>
<ul>
<li><a href="/documentation/development/bnd-testing-harness.html">BND Testing Harness</a></li>
@@ -88,7 +110,7 @@
<li><a href="/documentation/development/using-the-osgi-compliance-tests.html">Using the OSGi Compliance Tests</a></li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/development/bnd-testing-harness.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/development/bnd-testing-harness.html (original)
+++ websites/staging/felix/trunk/content/documentation/development/bnd-testing-harness.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,13 +77,24 @@
</div>
<h1>BND Testing Harness</h1>
- <h1 id="bnd-testing-harness">BND Testing Harness</h1>
+ <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>
+<h1 id="bnd-testing-harness">BND Testing Harness<a class="headerlink" href="#bnd-testing-harness" title="Permanent link">¶</a></h1>
<p>The latest versions of <a href="http://www.aqute.biz/Code/Bnd">BND</a> have testing harness capabilities for JUnit built in. In fact, the OSGi Alliance uses BND for its own build and testing system. BND already provided lots of support for creating bundles, so testing is perhaps a logical progression of those capabilities. This task was simplified by a proposed standard framework launching and embedding API for the OSGi R4.2 specification, which BND uses to configure and launch OSGi frameworks in a platform-independent way. I should note that this BND functionality is in its early stages, so there are some rough edges.</p>
<p>This document describes an example BND project used to test Felix' Framework and Logger subprojects. This document is not intended as a BND tutorial, since it is beyond my capabilities to describe how BND works. The goal is to document my hacked up example sufficiently so that other people can try it out for themselves. The original build files and configuration for this example are based on an example from Peter Kriens. BND also has an Eclipse plugin which makes it easy to run the test cases, but I have not experimented with that; this document works solely with the command line.</p>
<p>With that in mind, let's get started.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h2>
<p>This document assumes you have <a href="http://ant.apache.org">Ant</a>, [Maven|http://maven.apache.org], and Subversion installed. If you don't, please do this first.</p>
-<h2 id="getting-started">Getting Started</h2>
+<h2 id="getting-started">Getting Started<a class="headerlink" href="#getting-started" title="Permanent link">¶</a></h2>
<p>The first thing you need to do is check out the example with the following command:</p>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">felix</span><span class="o">/</span><span class="n">sandbox</span><span class="o">/</span><span class="n">rickhall</span><span class="o">/</span><span class="n">bnd</span><span class="o">-</span><span class="n">test</span>
</pre></div>
@@ -84,7 +106,7 @@
<p>The sole purpose of this POM file is to install our dependencies in the local Maven repository (i.e., <code>~/.m2/repository/</code>) so BND can find them. As a byproduct, it creates a <code>target/</code> directory, but this can be safely ignored. Using Maven is not strictly necessary, since we could just use BND's repository directly, but then we would need some way to populate its repository or would have to check the binaries into SVN. So, our Maven hybrid approach is not necessarily optimal, but it does allow us to capture the dependencies in a centralized POM file and easily populate the repository. Now we should be good to go.</p>
-<h2 id="the-setup">The Setup</h2>
+<h2 id="the-setup">The Setup<a class="headerlink" href="#the-setup" title="Permanent link">¶</a></h2>
<p>The important parts of the example are in the following directories:</p>
<ul>
<li><code>cnf</code> - This contains the default build setup and the BND repository.</li>
@@ -93,22 +115,22 @@
<li><code>org.apache.felix.log</code> - This contains the Felix Log Service and test cases.</li>
</ul>
<p>We will discuss the organization of each of these.</p>
-<h3 id="cnf"><code>cnf</code></h3>
+<h3 id="cnf"><code>cnf</code><a class="headerlink" href="#cnf" title="Permanent link">¶</a></h3>
<p>The default Ant build file <code>cnf/build.xml</code> is sufficiently generic and I didn't need to modify it, although it could probably be further cleaned up. The <code>cnf/build.bnd</code> sets up a lot of properties for BND, most of which I didn't touch. The main thing I modified in here was changing the <code>-runpath</code> to use the 1.5.0 version of Felix' Framework and configured BND's Maven plugin to use "<code>org.apache.felix</code>" as its <code>groupId</code>.</p>
-<h3 id="orgapachefelixframeworktest"><code>org.apache.felix.framework.test</code></h3>
+<h3 id="orgapachefelixframeworktest"><code>org.apache.felix.framework.test</code><a class="headerlink" href="#orgapachefelixframeworktest" title="Permanent link">¶</a></h3>
<p>This example is somewhat special since it tests the framework itself instead of a bundle, but even then it works basically the same as testing a bundle except that the framework is built separately. The project's <code>build.xml</code> file just includes the generic one from <code>cnf</code>, while the <code>bnd.bnd</code> file contains of the BND commands to create the resulting test bundle. We also use this file to specify the build path for the project and to indicate which classes are the test cases.</p>
<p>The source for the project is contained in the <code>src/</code> directory, but this is only source for the test cases. The <code>recipes/</code> directory contains additional <code>.bnd</code> files, which describe other bundles that get created and embedded into the resulting project bundle. If you look at the <code>Include-Resource</code> line in <code>bnd.bnd</code>, you can see that it instructs BND to include JAR files with names corresponding to the <code>.bnd</code> files in the <code>recipes/</code> directory. This is a cool feature, since it allows you to have a bunch of test code in the same project and generate any number of bundles from it, but these bundles don't actually exist in the file system or have to be managed. When embedding JAR files, BND searches for the JAR file or a <code>.bnd</code> file with a corresponding name to generate the JAR file. (This rule is actually set in the <code>cnf/build.bnd</code> file.)</p>
-<h3 id="orgapachefelixframeworkbootdelegation"><code>org.apache.felix.framework.bootdelegation</code></h3>
+<h3 id="orgapachefelixframeworkbootdelegation"><code>org.apache.felix.framework.bootdelegation</code><a class="headerlink" href="#orgapachefelixframeworkbootdelegation" title="Permanent link">¶</a></h3>
<p>This example, like the last, tests the framework itself. In theory, this test case could have been combined with the previous test cases, but since it is testing boot delegation, I didn't want it to potentially interfere with the other tests. It actually configures the <code>org.osgi.framework.bootdelegation</code> property in its <code>bnd.bnd</code>, so when BND launches the framework it uses this configuration property to determine how it performs boot delegation. If we combined this with the previous tests, then all of those tests would be impacted by this boot delegation value, which could cause some of them to behave improperly.</p>
<p>This is the case because all test cases within a given project are executed in one session in the same framework instance, which is a good reason that framework tests should always clean up after themselves (i.e., make sure all installed bundles are removed) because any leftover artifacts could interfere with subsequent tests. Therefore, if you have a test case that may interfere with other tests, you may want to create a separate project for it, like this one, so it runs in its own framework instance.</p>
<p>Like the previous project, the source for the test case is in the <code>src/</code> directory. This example does not embed any additional bundles.</p>
-<h3 id="orgapachefelixlog"><code>org.apache.felix.log</code></h3>
+<h3 id="orgapachefelixlog"><code>org.apache.felix.log</code><a class="headerlink" href="#orgapachefelixlog" title="Permanent link">¶</a></h3>
<p>This example tests the Felix Log Service bundle and actually demonstrates how you can include your tests cases within your project. The project's <code>build.xml</code> file just includes the generic one from <code>cnf</code>, while the <code>bnd.bnd</code> file contains the BND commands to create the resulting log service bundle. As before, we also specify the build path and the test cases for the project.</p>
<p>The source for the project is contained in the <code>src/</code> directory, which contains both the source for the Log Service and the test cases. This example doesn't embed any additional bundles.</p>
-<h2 id="running-the-examples">Running the Examples</h2>
+<h2 id="running-the-examples">Running the Examples<a class="headerlink" href="#running-the-examples" title="Permanent link">¶</a></h2>
<p>For the most part, all projects work the same way. We build them by typing <code>ant</code> and we can build and execute the tests by typing <code>ant test</code>. The results of the build are placed in the <code>tmp/</code> directory. To clean up, type <code>ant clean</code>, that's it. What actually happens is Ant is used to compile the source, while BND is used to create the resulting bundle. If you executed the tests, BND launches the framework, installs the bundle into it and starts it. Any test cases referenced in the <code>bnd.bnd</code> file are instantiated and their test methods are invoked. If the test cases have a <code>setBundleContext()</code> method, then they are injected with their bundle's context.</p>
<p>That is what is happening generically. Let's look in a little more detail at what each included example is doing.</p>
-<h3 id="orgapachefelixframeworktest_1"><code>org.apache.felix.framework.test</code></h3>
+<h3 id="orgapachefelixframeworktest_1"><code>org.apache.felix.framework.test</code><a class="headerlink" href="#orgapachefelixframeworktest_1" title="Permanent link">¶</a></h3>
<p>This example actually creates three test cases to test the framework itself, these test cases are:</p>
<ul>
<li><code>org.apache.felix.framework.test.TestClassLoading</code> - This test case verifies various class loading behavior.</li>
@@ -119,16 +141,16 @@
</ul>
<p>All of these test cases extend <code>org.apache.felix.framework.test.FelixTestCase</code>, which provides some helper functions, such as acquiring the bundle context and using <code>PackageAdmin</code> to refresh the framework. All source code for embedded bundles is in the same package tree and the test cases install them into the framework as needed by getting an input stream to the JAR resource.</p>
<p>By typing <code>ant test</code>, you should be able to run the test cases and get no errors.</p>
-<h3 id="orgapachefelixframeworkbootdelegation_1"><code>org.apache.felix.framework.bootdelegation</code></h3>
+<h3 id="orgapachefelixframeworkbootdelegation_1"><code>org.apache.felix.framework.bootdelegation</code><a class="headerlink" href="#orgapachefelixframeworkbootdelegation_1" title="Permanent link">¶</a></h3>
<p>This example has a single framework test case, <code>org.apache.felix.framework.bootdelegation.BootDelegationTest</code>, which performs various test to make sure the framework properly obeys the boot delegation property. This test is fairly simple and just directly extends the JUnit test case.</p>
<p>By typing <code>ant test</code>, you should be able to run the test case and get no errors.</p>
-<h3 id="orgapachefelixlog_1"><code>org.apache.felix.log</code></h3>
+<h3 id="orgapachefelixlog_1"><code>org.apache.felix.log</code><a class="headerlink" href="#orgapachefelixlog_1" title="Permanent link">¶</a></h3>
<p>This example builds the Log Service bundle (in package <code>org.apache.felix.log</code>) with one included test case (<code>test.TestLog</code>). This test case simply tests whether logged messages are added to the log properly and whether log listeners are properly handled. The test case is fairly simple and just directly extends the JUnit test case. If you need to run other bundles in addition to the bundle you are testing, you can specify their bundle symbolic names in <code>bnd.bnd</code> with the <code>-testbundles</code> option, according to Peter Kriens.</p>
<p>By typing <code>ant test</code>, you should be able to run the test case and get no errors.</p>
-<h2 id="conclusion">Conclusion</h2>
+<h2 id="conclusion">Conclusion<a class="headerlink" href="#conclusion" title="Permanent link">¶</a></h2>
<p>While not exhaustive, these examples show how BND can be used as a testing harness for the Felix Framework or as part of a complete build system for bundles. For my main use case, which is creating test cases for the framework, it definitely makes my life easier since I can just sit down and whip out some bundles to reproduce issues raised on the mailing lists without actually have to create separate bundle projects per se. Your mileage may vary.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project
Modified: websites/staging/felix/trunk/content/documentation/development/building-felix.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/development/building-felix.html (original)
+++ websites/staging/felix/trunk/content/documentation/development/building-felix.html Tue Sep 1 06:05:17 2015
@@ -39,7 +39,18 @@
</div>
<div class="menu">
- <p><a href="/news.html">news</a> <br />
+ <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><a href="/news.html">news</a> <br />
<a href="/license.html">license</a> <br />
<a href="/downloads.cgi">downloads</a> <br />
<a href="/documentation.html">documentation</a> <br />
@@ -66,7 +77,18 @@
</div>
<h1>Building Felix</h1>
- <h1 id="building-felix">Building Felix</h1>
+ <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>
+<h1 id="building-felix">Building Felix<a class="headerlink" href="#building-felix" title="Permanent link">¶</a></h1>
<p>A basic start to checking-out and building Felix:
1. Download and install the latest Maven 2 release.
1. Check out or update the Felix trunk (i.e., <code>svn checkout http://svn.apache.org/repos/asf/felix/trunk felix</code>).
@@ -76,7 +98,7 @@
1. If you want to create the installers, cd into <em>installers</em> and do a "mvn clean install", which will generate the installers in the installers/target/images/ directory.</p>
<p>-There is a simple build script in the trunk, called build_run.sh, that will build and run the framework for those that want a simple way to do all of this.-</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1422427 by fmeschbe on Sun, 16 Dec 2012 00:36:51 +0000
+ Rev. 1700393 by cziegeler on Tue, 1 Sep 2015 06:04:06 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project