felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fmesc...@apache.org
Subject svn commit: r1421893 [1/24] - in /felix/site/trunk/content: ./ documentation/ documentation/community/ documentation/development/ documentation/faqs/ documentation/subprojects/ documentation/subprojects/apache-felix-commons/ documentation/subprojects/a...
Date Fri, 14 Dec 2012 14:30:22 GMT
Author: fmeschbe
Date: Fri Dec 14 14:29:22 2012
New Revision: 1421893

URL: http://svn.apache.org/viewvc?rev=1421893&view=rev
Log:
FELIX-3816 First shot at converted content

Added:
    felix/site/trunk/content/documentation/
    felix/site/trunk/content/documentation.mdtext
    felix/site/trunk/content/documentation/community/
    felix/site/trunk/content/documentation/community.mdtext
    felix/site/trunk/content/documentation/community/apache-felix-community-roles-and-processes.mdtext
    felix/site/trunk/content/documentation/community/contributing-source-code.mdtext
    felix/site/trunk/content/documentation/community/contributing.mdtext
    felix/site/trunk/content/documentation/community/felix-r4-contributions.mdtext
    felix/site/trunk/content/documentation/community/projects-using-felix.mdtext
    felix/site/trunk/content/documentation/development/
    felix/site/trunk/content/documentation/development.mdtext
    felix/site/trunk/content/documentation/development/bnd-testing-harness.mdtext
    felix/site/trunk/content/documentation/development/building-felix.mdtext
    felix/site/trunk/content/documentation/development/coding-standards.mdtext
    felix/site/trunk/content/documentation/development/committers.mdtext
    felix/site/trunk/content/documentation/development/dependencies-file-template.mdtext
    felix/site/trunk/content/documentation/development/dependencies.mdtext
    felix/site/trunk/content/documentation/development/integrating-felix-with-eclipse.mdtext
    felix/site/trunk/content/documentation/development/integrating-felix-with-netbeans.mdtext
    felix/site/trunk/content/documentation/development/issue-tracking.mdtext
    felix/site/trunk/content/documentation/development/osgi-specification-implementations.mdtext
    felix/site/trunk/content/documentation/development/project-management-committee-pmc.mdtext
    felix/site/trunk/content/documentation/development/provisional-osgi-api-policy.mdtext
    felix/site/trunk/content/documentation/development/release-management-nexus.mdtext
    felix/site/trunk/content/documentation/development/roadmap.mdtext
    felix/site/trunk/content/documentation/development/source-code.mdtext
    felix/site/trunk/content/documentation/development/svn-repository-structure.mdtext
    felix/site/trunk/content/documentation/development/using-the-osgi-compliance-tests.mdtext
    felix/site/trunk/content/documentation/faqs/
    felix/site/trunk/content/documentation/faqs.mdtext
    felix/site/trunk/content/documentation/faqs/apache-felix-bundle-plugin-faq.mdtext
    felix/site/trunk/content/documentation/faqs/apache-felix-scr-plugin-faq.mdtext
    felix/site/trunk/content/documentation/getting-started.mdtext
    felix/site/trunk/content/documentation/subprojects/
    felix/site/trunk/content/documentation/subprojects.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-commons/
    felix/site/trunk/content/documentation/subprojects/apache-felix-commons.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-commons/creating-bundles-using-bnd.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-config-admin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-background.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-getting-started.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-introduction.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-migrating-from-earlier-versions.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-osgi-design-patterns.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-reference-guide.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-how-to-build.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-using-annotations-components.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-using-annotations-composition.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-using-annotations-dependencies.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-using-annotations-lifecycle.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-using-annotations-quick-tour/
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-using-annotations-quick-tour.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/apache-felix-dependency-manager-using-annotations/apache-felix-dependency-manager-using-annotations-quick-tour/apache-felix-dependency-manager-using-annotations-quick-start.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/dependency-manager-background.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/dependency-manager-design.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/dependency-manager-shell.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-dependency-manager/dependency-manager-usage.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-deployment-admin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-event-admin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-file-install.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework-security.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-alternative-java-vms.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-and-google-android.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-bundle-cache.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-faq.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-launching-and-embedding.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-2-ct-results.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-osgi-r4-3-ct-results.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-gogo/
    felix/site/trunk/content/documentation/subprojects/apache-felix-gogo.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-gogo/rfc-147-overview.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-http-service.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/dive-into-the-ipojo-manipulation-depths.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-use-ipojo-manipulation-metadata.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/how-to-write-your-own-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-devguide/ipojo-concepts-overview.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-eclipse-integration.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-feature-overview.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/apache-felix-ipojo-dosgi.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-advanced-tutorial.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-composition-tutorial.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-hello-word-maven-based-tutorial.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-gettingstarted/ipojo-in-10-minutes.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-header/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-header.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-header/apache-felix-ipojo-footer.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-issuestracker.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-architecture.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-maven.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-methods.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-junit4osgi/apache-felix-ipojo-junit4osgi-tutorial.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-keypoints.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-menu.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-online-manipulator.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-pagemenu.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-successstories.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedosgi.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-supportedvms.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-testing-components.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-ant-task.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-arch-command.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-eclipse-plug-in.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-maven-plug-in.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/ipojo-webconsole-plugin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-tools/junit4osgi.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/apache-felix-ipojo-api.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/architecture-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/configuration-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/controller-lifecycle-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/event-admin-handlers.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/extender-pattern-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/ipojo-jmx-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/lifecycle-callback-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/providing-osgi-services.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/service-requirement-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/temporal-service-dependency.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/describing-components/white-board-pattern-handler.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/how-to-use-ipojo-annotations.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/combining-ipojo-and-configuration-admin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/constructing-pojo-objects-with-factory-methods.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/how-to-use-ipojo-factories.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/ipojo-hierarchical-composition-overview.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-advanced-topics/using-ipojo-introspection-api.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/ipojo-faq.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-userguide/using-xml-schemas.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/apache-felix-ipojo-why-choose-ipojo.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/article-presentations.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/developing-camel-mediators-with-ipojo.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/download.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/future-ideas.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/handlers-proposition.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-news.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-reference-card.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-support.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/ipojo-test-page.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/menu2.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-ipojo/related-works.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-lightweight-http-service.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-log.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-manifest-generator-mangen.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-obr-plugin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-osgi-plugin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-maven-scr-plugin-use.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/apache-felix-scr-ant-task-use.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/extending-scr-annotations.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-maven-scr-plugin/scr-javadoc-tags.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-metatype-service.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-osgi-bundle-repository.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-osgi-core.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-preferences-service.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-remote-shell.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-serialization-framework.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-service-component-runtime.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-shell-tui.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-shell.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-contributing.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features/
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features/apache-felix-sigil-eclipse/
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features/apache-felix-sigil-eclipse.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-key-features/apache-felix-sigil-eclipse/apache-felix-sigil-eclipse-features.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-road-map.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-installation.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-quickstart.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-ivy/apache-felix-sigil-ivy-settings.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-junit.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-projects.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-properties.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-filesystem.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-sigil/sigil-user-guide/sigil-repositories/apache-felix-sigil-obr.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-acknowledgments.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-driver-architecture.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-getting-started.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-known-issues.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples/
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-upnp/upnp-testing-devices/upnp-examples/upnp-writing-cd-and-cp.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-user-admin/
    felix/site/trunk/content/documentation/subprojects/apache-felix-user-admin.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-background.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-file-store.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-getting-started.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-introduction.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-user-admin/apache-felix-user-admin-mongodb-store.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/branding-the-web-console.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/providing-resources.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/providing-web-console-plugins.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/web-console-logging.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/extending-the-apache-felix-web-console/web-console-output-templating.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/web-console-restful-api.mdtext
    felix/site/trunk/content/documentation/subprojects/apache-felix-web-console/web-console-security-provider.mdtext
    felix/site/trunk/content/documentation/subprojects/mosgi-managed-osgi-framework/
    felix/site/trunk/content/documentation/subprojects/mosgi-managed-osgi-framework.mdtext
    felix/site/trunk/content/documentation/subprojects/mosgi-managed-osgi-framework/probeguide.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-application-demonstration.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-faq.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-1.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-2.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-2b.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-3.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-4.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-5.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-6.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-7.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/apache-felix-osgi-tutorial/apache-felix-tutorial-example-8.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/checking-out-and-building-felix-with-netbeans.mdtext
    felix/site/trunk/content/documentation/tutorials-examples-and-presentations/presentations.mdtext
    felix/site/trunk/content/downloads.mdtext
    felix/site/trunk/content/license.mdtext
    felix/site/trunk/content/links.mdtext
    felix/site/trunk/content/mailinglists.mdtext
    felix/site/trunk/content/media.mdtext
    felix/site/trunk/content/miscellaneous/
    felix/site/trunk/content/miscellaneous.mdtext
    felix/site/trunk/content/miscellaneous/apache-karaf.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/
    felix/site/trunk/content/miscellaneous/board-reports.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/apache-felix-board-report-template.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2007-04.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2007-05.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2007-06.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2007-09.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2007-12.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2008-03.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2008-06.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2008-09.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2008-12.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2009-03.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2009-06.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2009-09.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2009-12.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2010-03.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2010-06.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2010-09.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2010-12.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2011-03.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2011-06.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2011-09.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2011-12.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2012-03.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2012-06.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2012-09.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2012-12.mdtext
    felix/site/trunk/content/miscellaneous/board-reports/board-report-2013-03.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-001-use-cases.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-002-profiles/
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-002-profiles.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-002-profiles/cat-scan-002-001-basic-profile.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-003-run-log-archive.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-004-api-reference.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-005-technical-compatibility-kit.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-006-glossary.mdtext
    felix/site/trunk/content/miscellaneous/cat-scan-project-proposal/cat-scan-007-references.mdtext
    felix/site/trunk/content/miscellaneous/incubator-status-report-january-2007.mdtext
    felix/site/trunk/content/miscellaneous/incubator-status-report-october-2006.mdtext
    felix/site/trunk/content/miscellaneous/osgi-bundle-service-diagrams.mdtext
    felix/site/trunk/content/miscellaneous/sandbox/
    felix/site/trunk/content/miscellaneous/sandbox.mdtext
    felix/site/trunk/content/miscellaneous/sandbox/composite-bundles.mdtext
    felix/site/trunk/content/miscellaneous/sandbox/virtual-bundles.mdtext
    felix/site/trunk/content/miscellaneous/sandbox/web-console-ng.mdtext
    felix/site/trunk/content/miscellaneous/subproject-release-status.mdtext
    felix/site/trunk/content/miscellaneous/tlp-task-list.mdtext
    felix/site/trunk/content/navigation.mdtext
    felix/site/trunk/content/news.mdtext
    felix/site/trunk/content/res/
    felix/site/trunk/content/res/apache.png   (with props)
    felix/site/trunk/content/res/codehilite.css
    felix/site/trunk/content/res/favicon.ico   (with props)
    felix/site/trunk/content/res/favicon.png   (with props)
    felix/site/trunk/content/res/gradient.png   (with props)
    felix/site/trunk/content/res/logo.png   (with props)
    felix/site/trunk/content/res/old_felix_site.css
    felix/site/trunk/content/res/pygments-friendly.css
    felix/site/trunk/content/res/site.css
    felix/site/trunk/content/wiki.mdtext
Modified:
    felix/site/trunk/content/index.mdtext
    felix/site/trunk/content/sitemap.html

Added: felix/site/trunk/content/documentation.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation.mdtext (added)
+++ felix/site/trunk/content/documentation.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,16 @@
+Title: documentation
+
+# Documentation
+
+*The Felix web site and documentation are maintained on our [wiki](http://cwiki.apache.org/confluence/x/O-).*
+
+In an effort to make it easier to find desired documentation, we have divided our documentation section into the following six areas:
+
+* [Getting started]({{ refs.getting-started.path }}) - This area captures a few links from the areas below that will help you get started with Felix.
+* [FAQs]({{ refs.faqs.path }}) - This area captures all FAQ documentation, which typically varies from subproject to subproject.
+* [Community]({{ refs.community.path }}) - This area captures documentation associated with how the Felix community works and how to become involved in it.
+* [Development]({{ refs.development.path }}) - This area captures documentation for Felix developers or those interested in becoming Felix developers; this is not intended for Felix users although some information may be useful.
+* [Subprojects]({{ refs.subprojects.path }}) - This area captures user documentation for the various Felix subprojects.
+* [Tutorials, examples, and presentations]({{ refs.tutorials-examples-and-presentations.path }}) - This area captures general user documentation that does not necessarily fit into any single subproject.
+
+If you are unable to find the documentation you need, please ask on the [mailing lists]({{ refs.mailinglists.path }}). Also, feedback on improving the documentation and/or organization of this site is welcome.

Added: felix/site/trunk/content/documentation/community.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/community.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/community.mdtext (added)
+++ felix/site/trunk/content/documentation/community.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,5 @@
+Title: Community
+
+# Community Documentation
+
+{children}
\ No newline at end of file

Added: felix/site/trunk/content/documentation/community/apache-felix-community-roles-and-processes.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/community/apache-felix-community-roles-and-processes.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/community/apache-felix-community-roles-and-processes.mdtext (added)
+++ felix/site/trunk/content/documentation/community/apache-felix-community-roles-and-processes.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,43 @@
+Title: Apache Felix Community Roles and Processes
+
+# Roles
+
+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.
+
+## Users
+
+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 *Contributor*.
+
+## Contributors
+
+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.
+
+## Committers
+
+Contributors who give frequent and valuable contributions to a subproject of Felix can have their status promoted to that of a *Committer*. A Committer has write access to Felix' source code repository.
+
+## PMC Members
+
+Committers who frequently participate with valuable contributions may have their status promoted to that of a *PMC member*. This committee is the official managing body of project and is responsible for setting its overall direction.
+
+# Processes
+
+## Becoming a User or Contributor
+
+There is no requirement for becoming a User or Contributor; these roles are open to everyone.
+
+## Becoming a Committer
+
+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.
+
+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.
+
+## Becoming a PMC Member
+
+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.
+
+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.
+
+### Exceptions
+
+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.
\ No newline at end of file

Added: felix/site/trunk/content/documentation/community/contributing-source-code.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/community/contributing-source-code.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/community/contributing-source-code.mdtext (added)
+++ felix/site/trunk/content/documentation/community/contributing-source-code.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,32 @@
+Title: Contributing Source Code
+
+# Source Code Contributions
+
+Source code contributions fall into two categories: patches or grants. This document describes both and how to handle each.
+
+## Patches
+
+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:
+
+1. Create a [JIRA](http://issues.apache.org/jira/browse/Felix) issue (or find a pertinent existing issue) describing the issue needing to be addressed.
+1. Attach the patch (in the form of a diff) to the above issue and describe how the patch addresses the issue.
+1. If you intend to have your patch used by us, make sure you *grant Apache the rights to use it* when you attach the patch to the issue.
+1. The patch will eventually be reviewed and applied (if accepted) by a Felix committer, but feel free to bug us \[nicely\]({{ refs.nicely.path }}) if you get impatient.
+
+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. :-)
+
+## Grants
+
+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:
+
+1. Verify that you have the authorization to donate the code.
+1. Review our [developer documentation]({{ refs.development.path }}) as well as the general [Apache documentation|http://www.apache.org/foundation/getinvolved.html] to determine whether you would really like be involved with us and how we work.
+1. Assuming you're still interested, create a [JIRA](http://issues.apache.org/jira/browse/Felix) issue describing the code you wish to donate.
+1. Attach an archive containing the code along with an MD5 signature of the archive to the above issue. You should remove any existing headers from the source files and add the standard Apache header to each. Note that you keep the rights to your code and can do anything with it you want, you will just grant us the right to use it too.
+1. Allow the community time to discuss the contribution, after which a vote will be called to accept the contribution.
+1. If the vote passes, then you will need to submit a [software grant](http://www.apache.org/licenses/software-grant.txt) form.
+1. It is also a good idea to submit an [ICLA](http://www.apache.org/licenses/icla.txt) to ease future contributions. Depending on the company you work for, they may also want to contribute a [CCLA|http://www.apache.org/licenses/cla-corporate.txt], although this isn't strictly necessary from an Apache point of view, since it is your responsibility to verify your ability to submit an ICLA.
+1. Once all of this information is received, then we will gather it and perform [IP clearance](http://incubator.apache.org/ip-clearance/index.html).
+1. After a few days, if no red flags are raised, then we'll commit the code and we're good to go.
+
+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.
\ No newline at end of file

Added: felix/site/trunk/content/documentation/community/contributing.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/community/contributing.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/community/contributing.mdtext (added)
+++ felix/site/trunk/content/documentation/community/contributing.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,20 @@
+Title: Contributing
+
+# Contributing
+
+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 [Community Roles and Processes]({{ refs.apache-felix-community-roles-and-processes.path }}) document and/or join the [mailing lists|mailinglists].
+
+The Felix project organizes its "to do" list using the [JIRA](http://issues.apache.org/jira/browse/Felix) 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.
+
+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.
+
+## Non-Programmers
+
+* 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 [Documentation](http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12310100&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12312255) component.
+* Define a compatibility documentation legend for bundle subprojects. [FELIX-537](http://issues.apache.org/jira/browse/FELIX-537)
+
+## Programmers
+
+* Write tests for the framework and/or its sub-projects, either using JUnit or the new [BND testing harness](http://felix.apache.org/site/bnd-testing-harness.html)
+* Work on an installer that can install Felix as a daemon/service. [Installer issues](https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=12310100&sorter/order=DESC&sorter/field=priority&resolution=-1&component=12310803)
+* Browse issues in [JIRA](http://issues.apache.org/jira/browse/Felix) and submit a patch.

Added: felix/site/trunk/content/documentation/community/felix-r4-contributions.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/community/felix-r4-contributions.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/community/felix-r4-contributions.mdtext (added)
+++ felix/site/trunk/content/documentation/community/felix-r4-contributions.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,66 @@
+Title: Felix R4 contributions
+
+# Felix R4 OSGi Service Platform Contributions
+
+These are the recorded contributions:
+  
+  
+  
+  
+| 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 | [Result](http://mail-archives.apache.org/mod_mbox/incubator-felix-dev/200704.mbox/%3c46167210.9080109@ungoverned.org%3e) | Grant and ICLA | Yes |
+  
+  
+  
+  
+| org.osgi.service.device | The OSGi Device Access Package. | | | | |
+  
+  
+  
+  
+| org.osgi.service.io | The OSGi IO Connector Specification Version 1.0. | Pending, To Be Announced | | | |
+  
+  
+| org.osgi.service.metatype | The OSGi Metatype Package. | Felix Meschberger | [Result](http://mail-archives.apache.org/mod_mbox/incubator-felix-dev/200704.mbox/%3c46167210.9080109@ungoverned.org%3e) | Grant and ICLA | Yes |
+  
+  
+  
+  
+  
+  
+| org.osgi.service.provisioning | The OSGi Provisioning Service Package. | | | | |
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+  
+| org.osgi.util.measurement | The OSGi Measurement Package. | Reference | | | |
+| org.osgi.util.position | The OSGi Position Package. | Reference | | | |
+| org.osgi.util.tracker | The OSGi Service Tracker Package. | Reference | | | |
+| org.osgi.util.xml | The OSGi XML Parser service Package. | Reference | | | |
+  
+  
+  
+  
+  
+  
+| org.apache.felix.shell.remote | Remote Shell | Dieter Wimberger | [Result](http://markmail.org/message/k2yd6zsrsifloelp) | [IP Clearance|http://incubator.apache.org/ip-clearance/felix-remote-shell.html] | Yes |
+
+Send comments to the [Felix developers mailinglist]({{ refs.mailinglists.path }}).
\ No newline at end of file

Added: felix/site/trunk/content/documentation/community/projects-using-felix.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/community/projects-using-felix.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/community/projects-using-felix.mdtext (added)
+++ felix/site/trunk/content/documentation/community/projects-using-felix.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,13 @@
+Title: Projects Using Felix
+
+This page highlights projects that use Apache Felix (listed alphabetically):
+
+* [Apache Karaf](http://karaf.apache.org) - A small, OSGi-based runtime that provides a lightweight container into which various components and applications can be deployed (formerly an Apache Felix subproject).
+* [Apache ServiceMix](http://servicemix.apache.org/) - an Enterprise Service Bus (using Felix via Karaf).
+* [Apache Sling](http://incubator.apache.org/sling/) - a JCR content based web application framework
+* [Apache Tuscany](http://incubator.apache.org/tuscany/) - an open source implementation of [SCA|http://www.oasis-opencsa.org/].
+* [Ascert VersaTest](http://www.ascert.com/) - enterprise system testing platform
+* [DySoWeb](http://www.requea.com/dysoweb/rq/en/archi/dysoweb) - A platform for dynamic component deployment.
+* [GlassFish](http://glassfish.dev.java.net) - JavaEE application server.
+* [OW2 JOnAS](http://jonas.ow2.org/) - JavaEE application server.
+* [SIP Communicator](https://sip-communicator.dev.java.net/) - a multi-protocol instant messenger and SIP software phone.

Added: felix/site/trunk/content/documentation/development.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/development.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/development.mdtext (added)
+++ felix/site/trunk/content/documentation/development.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,7 @@
+Title: Development
+
+# Development
+
+This page contains links related to Felix project development.
+
+{children}
\ No newline at end of file

Added: felix/site/trunk/content/documentation/development/bnd-testing-harness.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/development/bnd-testing-harness.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/development/bnd-testing-harness.mdtext (added)
+++ felix/site/trunk/content/documentation/development/bnd-testing-harness.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,100 @@
+Title: BND Testing Harness
+
+# BND Testing Harness
+
+The latest versions of [BND](http://www.aqute.biz/Code/Bnd) 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.
+
+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.
+
+With that in mind, let's get started.
+
+## Prerequisites
+
+This document assumes you have [Ant](http://ant.apache.org), [Maven|http://maven.apache.org], and Subversion installed. If you don't, please do this first.
+
+## Getting Started
+
+The first thing you need to do is check out the example with the following command:
+
+
+    svn co http://svn.apache.org/repos/asf/felix/sandbox/rickhall/bnd-test
+
+
+The above command will create a directory called `bnd-test`, so go into that directory. Before we can perform the tests, we need to get some dependent libraries for our setup. Similar to Maven, BND has a repository concept, which in this example will be rooted in `bnd-test/cnf/repo`. However, this example does not use this repository except for the BND library itself; instead, we leverage Maven's existing repositories to get our dependencies. Luckily, BND's repository has a plugin to get it to search the local Maven repository for needed JAR files, all we need to do is populate our local Maven repository with what we need. The example includes a `pom.xml` file for this purpose, so we just need to type:
+
+
+    mvn install
+
+
+The sole purpose of this POM file is to install our dependencies in the local Maven repository (i.e., `~/.m2/repository/`) so BND can find them. As a byproduct, it creates a `target/` 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.
+
+## The Setup
+
+The important parts of the example are in the following directories:
+
+* `cnf` - This contains the default build setup and the BND repository.
+* `org.apache.felix.framework.test` - This contains some test cases for the Felix Framework.
+* `org.apache.felix.framework.bootdelegation` - This contains a boot delegation test case for the Felix Framework.
+* `org.apache.felix.log` - This contains the Felix Log Service and test cases.
+
+We will discuss the organization of each of these.
+
+### `cnf`
+
+The default Ant build file `cnf/build.xml` is sufficiently generic and I didn't need to modify it, although it could probably be further cleaned up. The `cnf/build.bnd` 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 `-runpath` to use the 1.5.0 version of Felix' Framework and configured BND's Maven plugin to use "`org.apache.felix`" as its `groupId`.
+
+### `org.apache.felix.framework.test`
+
+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 `build.xml` file just includes the generic one from `cnf`, while the `bnd.bnd` 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.
+
+The source for the project is contained in the `src/` directory, but this is only source for the test cases. The `recipes/` directory contains additional `.bnd` files, which describe other bundles that get created and embedded into the resulting project bundle. If you look at the `Include-Resource` line in `bnd.bnd`, you can see that it instructs BND to include JAR files with names corresponding to the `.bnd` files in the `recipes/` 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 `.bnd` file with a corresponding name to generate the JAR file. (This rule is actually set in the `cnf/build.bnd` file.)
+
+### `org.apache.felix.framework.bootdelegation`
+
+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 `org.osgi.framework.bootdelegation` property in its `bnd.bnd`, 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.
+
+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.
+
+Like the previous project, the source for the test case is in the `src/` directory. This example does not embed any additional bundles.
+
+### `org.apache.felix.log`
+
+This example tests the Felix Log Service bundle and actually demonstrates how you can include your tests cases within your project. The project's `build.xml` file just includes the generic one from `cnf`, while the `bnd.bnd` 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.
+
+The source for the project is contained in the `src/` directory, which contains both the source for the Log Service and the test cases. This example doesn't embed any additional bundles.
+
+## Running the Examples
+
+For the most part, all projects work the same way. We build them by typing `ant` and we can build and execute the tests by typing `ant test`. The results of the build are placed in the `tmp/` directory. To clean up, type `ant clean`, 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 `bnd.bnd` file are instantiated and their test methods are invoked. If the test cases have a `setBundleContext()` method, then they are injected with their bundle's context.
+
+That is what is happening generically. Let's look in a little more detail at what each included example is doing.
+
+### `org.apache.felix.framework.test`
+
+This example actually creates three test cases to test the framework itself, these test cases are:
+
+* `org.apache.felix.framework.test.TestClassLoading` - This test case verifies various class loading behavior.
+* `org.apache.felix.framework.test.TestConcurrency` - This test case tries to deadlock the framework.
+* `org.apache.felix.framework.test.TestFilter` - This test case directly tests filter functionality.
+* `org.apache.felix.framework.test.TestFragment` - This test case checks host and fragment resolution.
+* `org.apache.felix.framework.test.TestResolver` - This test cases verifies resolver behavior.
+
+All of these test cases extend `org.apache.felix.framework.test.FelixTestCase`, which provides some helper functions, such as acquiring the bundle context and using `PackageAdmin` 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.
+
+By typing `ant test`, you should be able to run the test cases and get no errors.
+
+### `org.apache.felix.framework.bootdelegation`
+
+This example has a single framework test case, `org.apache.felix.framework.bootdelegation.BootDelegationTest`, 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.
+
+By typing `ant test`, you should be able to run the test case and get no errors.
+
+### `org.apache.felix.log`
+
+This example builds the Log Service bundle (in package `org.apache.felix.log`) with one included test case (`test.TestLog`). 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 `bnd.bnd` with the `-testbundles` option, according to Peter Kriens.
+
+By typing `ant test`, you should be able to run the test case and get no errors.
+
+## Conclusion
+
+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.
\ No newline at end of file

Added: felix/site/trunk/content/documentation/development/building-felix.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/development/building-felix.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/development/building-felix.mdtext (added)
+++ felix/site/trunk/content/documentation/development/building-felix.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,13 @@
+Title: Building Felix
+
+# Building Felix
+
+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., `svn checkout http://svn.apache.org/repos/asf/felix/trunk felix`).
+1. -Perform an "mvn clean install" in the trunk to clean and build everything. Due to a bug in Maven related to having multiple packaging plugins in the same project, this step no longer works. We were forced to split our POM file into profiles that group subprojects according to the packaging plugin they use; to build everything, we created an Ant build.xml file. Simply type "ant" to do the equivalent of "mvn clean install" or do "ant clean" or "ant install" to do "mvn clean" or "mvn install", respectively.-
+1. Go to the top of the project and type: "mvn -Dpackaging=plugins install" and then "mvn -Dpackaging=bundle install" to build the project.
+1. To run the newly built framework, cd into *main* and type "java \-jar bin/felix.jar".
+1. If you want to create the installers, cd into *installers* and do a "mvn clean install", which will generate the installers in the installers/target/images/ directory.
+
+-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.-
\ No newline at end of file

Added: felix/site/trunk/content/documentation/development/coding-standards.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/development/coding-standards.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/development/coding-standards.mdtext (added)
+++ felix/site/trunk/content/documentation/development/coding-standards.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,483 @@
+Title: Coding Standards
+
+# Coding standards
+
+## Guidelines Summary
+
+This style guide is intended to help the computer professional produce better Java programs. It presents a set of specific guidelines for using the features of Java in a disciplined manner. The goal is to develop high quality, reliable, reusable, portable software. For a number of reasons, no programming language can ensure the achievements of these desirable objectives on its own. Programming must be embedded in a disciplined development process that addresses a number of topics in a well managed way. The use of Java is one of those. It must conform to good programming practices be based on well established software engineering principles. This style guide is intended to bridge the gap between these principles and the actual practice of programming in Java.
+
+Clear, readable, understandable source text eases program evolution, adaptation and maintenance. First, such source text is more likely to be correct and reliable. Second, effective code adaptation is a prerequisite to code reuse, a technique that has the potential for drastic reductions in system development costs. Easy adaptation requires thorough understanding of the software, and that is facilitated considerably by clarity. Finally, since maintenance (really evolution) is a costly process that continues throughout the life of a system, clarity plays a major role in keeping maintenance costs down. Over the entire life cycle, code has to be read and understood far more often than it is written; the investment of effort in writing readable, understandable code is thus well worthwhile. Many of the guidelines in this style guide are designed to promote clarity of the source text.
+
+This style guide is intended for those involved in the development of real software systems written in Java. Different roles in a software project can exploit the style guide in different ways. The programmer can use it as a reference on good Java style. It can be used in code reviews as a common reference. Finally, lessons learned in real projects can be captured by extending the style guide.
+  
+## Class layout and comments
+
+### Files and filenames
+
+Files longer than 2000 lines are cumbersome and should be avoided.
+
+#### File names
+
+The file must be named after the class it represents. As for most cases each file contains only one class, this is an easy naming convention. For nested or inner classes the name of the main class must be the name of the file. As names in Java are case-sensitive, the filename is case-sensitive also.
+
+#### File organization
+
+Each Java source file contains a single class or interface. Of course, this excludes inner classes as these must be defined without an (outer) class, and thus in the same file.
+
+Java source files have the following ordering:
+
+- Beginning comments
+- Package and import statements
+- Class and interface declarations
+ 
+#### Beginning comments
+
+All source files must begin with the comments shown in the following code sample.
+
+
+    /*
+     * Licensed to the Apache Software Foundation (ASF) under one
+     * or more contributor license agreements.  See the NOTICE file
+     * distributed with this work for additional information
+     * regarding copyright ownership.  The ASF licenses this file
+     * to you under the Apache License, Version 2.0 (the
+     * "License"); you may not use this file except in compliance
+     * with the License.  You may obtain a copy of the License at
+     *
+     *   http://www.apache.org/licenses/LICENSE-2.0
+     *
+     * Unless required by applicable law or agreed to in writing,
+     * software distributed under the License is distributed on an
+     * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+     * KIND, either express or implied.  See the License for the
+     * specific language governing permissions and limitations
+     * under the License.
+     */
+
+
+Note that this comment part is not according to the JavaDoc style (See: How to write doc comments for JavaDoc - Sun Microsystems, Inc.) as this is file specific information that is not relevant in generated API documentation.
+
+##### Package and import Statements
+
+The first non-comment line of most Java source files is a package statement. After an empty line import statements can follow. For example:
+
+
+    package org.apache.felix.whatever.this.is;
+    
+    import java.awt.Frame;
+    import java.io.InputStream;
+    import java.util.Vector;
+
+
+A few notes must be made here:
+1. Package rules.
+  When not using an explicit package statement in your code the code still is in a package, the default package. This easily results in name clashes and as package naming should be a part of the design, always use an explicit package name. For naming rules of packages see 3.4 Naming conventions.
+1. Import statements need to be explicit in order to overcome name clashes.
+  They should be grouped by name. When the number of import statements of the same package exceeds the 'readability' limit (please use common sense), then import the complete package by adding '.*'.
+1. Import order.
+  First in this section should be the standard Java imports like: java.lang.Throwable. Second should be the Java extensions (i.e. javax), third, the third party stuff. Finally the project-specific imports should be added.
+
+##### Class and interface Declarations
+
+The following comment block is an example for the comment that belongs to the declaration of a class or an interface. The combination of JavaDoc syntax and keywords that are expanded by the source integrity tool result in the following block:
+
+
+    /**
+     * This class is not really a class, because this file is just
+     * a template that shows how the file header and class header
+     * should look like.
+     *
+     * @author <a href="mailto:dev@felix.apache.org">Felix Project Team</a>
+     */
+
+
+The following table describes the parts of a class or interface declaration, in the order that they should appear.
+
+| Part of Class/Interface Declaration | Notes |
+|--|--|
+|Class/Interface documentation|According to comment block as shown above.|
+|Class or interface statement| |
+|Class (static) variables|These should be grouped by functionality rather than by scope.|
+|Instance variables|These should be grouped by functionality rather than by scope.|
+|Constructors|Start with the default constructor if any.|
+|Methods that belong to the class (see also 2.1.3.4 Class methods versus specific interface methods and event methods)|These methods should also be grouped by functionality rather than by scope or accessibility. E.g. a private class method can be in between two public instance methods. The goal is to make reading and understanding the code easier. When implementing an interface, group the methods that are part of the interface.|
+|Methods of interfaces that are implemented by the class.|Automatically grouped by functionality if grouped by interface.|
+|Inner classes|As they are only visible within their top-level class, they are placed at the bottom of the file.|
+
+### Indentation
+
+Four spaces should be used as unit of indentation. Use spaces or let your editor convert tabs to spaces as some editors might show the tabs different than they were intended! Tabs must be set exactly every 4 spaces.
+
+#### Line length
+
+There is no explicit limit for the length of a line. Make sure that the flow of the code is clear and that, when printing the file, it is well formed when using a reasonable font. A reasonable length would be around 80 characters.
+
+#### Wrapping lines
+
+When an expression will not fit on a single line, break it according to these general principles:
+- break after a comma;
+- break before an operator;
+- prefer higher level breaks to lower level breaks;
+- align the new line with the beginning of the expression after the assignment;
+- if the above rules lead to confusing code or to code that's squished up against the right margin, please use common sense.
+
+Some examples breaking an arithmetic expression. The first is preferred, since the break occurs outside the parenthesised expression:
+
+
+    longName1 = longName2 * (longName3 + longName4 - longName5)
+        + 4; // preferred
+    longName1 = longName2 * (longName3 + longName4 
+        - longName5) + 4;
+
+
+### Comment
+
+#### Comment styles
+
+The Java language supports three different kinds of comments:
+
+
+    // text 
+
+
+The compiler ignores everything from // to the end of the line. Use this style when adding a description or some kind of explanation at the same line of code. 
+
+
+    /* text */ 
+
+
+The compiler ignores everything from /* to */. The next documentation style is preferred.
+
+
+    /** Documentation. */ 
+
+
+This indicates a documentation comment (doc comment, for short). The compiler ignores this kind of comment, just like it ignores comments that use /* and */. The JDK JavaDoc tool uses doc comments when preparing automatically generated documentation (See: JavaDoc keywords and HTML tags). But JavaDoc only uses this documentation when it occurs at an expected position in the file like the class definition or a member declaration. 
+
+#### Block comments
+
+Block comments are used to provide English descriptions of the contents of files, the task of methods and the description of data structures and algorithms. Block comments should be used at the beginning of each file and before each method. They can also be used in other places, such as within methods.
+
+For a description of class comment see 2.1.3.3 Class and Interface Declarations. A method block comment looks as follows:
+
+
+    /**
+     * Position the splitter location at a specified position.
+     * This method can for instance be used when the last position
+     * is stored as a preference setting for the user.
+     *
+     * @param position  New position of divider, defined in pixels
+     *     from the left of the containing window
+     * @see com.sun.java.swing.JSplitPane
+     * @exception org.apache.felix.player.PositionException
+     *     Whenever an invalid position is passed.
+     */
+    public void setSplitterLocation(int position) throws PositionException
+
+
+#### JavaDoc keywords and HTML tags
+
+For class headers, method headers and member variables JavaDoc is used in order to generate API documentation from the source later on (See: JavaDoc homepage - Sun Microsystems, Inc.).
+A few specific JavaDoc keywords are:
+
+|Keyword|Short description|
+|--|--|
+|@version|Can be used to label a specific version of a package or application so the documentation shows this version number also.|
+|@author|The name entered here is shown as the author.|
+|@param|Used to define one parameter and describe this parameter.|
+|@see|When there are similarities with another class this tag is used to offer the reader a hyperlink to the mentioned class.|
+|@exception or @throws|Offered as hyperlink to the exception that can be thrown by a method.|
+|@return|Return value of a method|
+
+Some HTML-tags that can be used in order to make the comment blocks more readable:
+
+|Tag|Short description|
+|--|--|
+|<p>|New paragraph.|
+|<br>|Break, a carriage return. For separation of two paragraphs, usage of <p> is preferred.|
+|<ul><li></li></ul>|Unordered list of items; each item should start with a <li> tag. By most browsers, this is formatted as a bulleted list.|
+|<code></code>|Code samples; use this when refering to class names, method names, parameter names, etc.|
+|<pre></pre>|Preformatted text. Use these tags to protect figures and schemas "drawn" in Ascii, against formatting by the browser (which normally ignores whitespace and line breaks)|
+|<dl><dt></dt><dd></dd></dl>|Definition lists; <dt> specifies the term that is defined and <dd> the definition of this term. Not frequently used.|
+
+Note: there is no need to embed the parameter name in the @param tag in <code> tags; this is done by javadoc automatically. The same holds for the exception name in the @exception or @throws tag. In the clarifying text however, use the <code> tags when refering to parameter names etc. The example below shows the <code> tag being used for the array parameter in the text, but not in its definition. 
+
+Example:
+
+    /**
+     * Prints a range from an object array. The range
+     * is specified by the first element to print, and
+     * ranges to the last element of the array.
+     *
+     * @param array contains the objects to print
+     * @param first index of first element in 
+     *     the <code>array</code> to print
+     */
+    public void printRange(Object[] array, int first)
+
+ 
+## Java syntax and its layout
+
+### Declarations
+
+When declaring a variable or method make the accessibility as restrictive as possible. When using multiple keywords use the following ordering of keywords:
+
+1. accessibility
+  Start with the accessibility as it makes clear if the method or variable is reachable at all.
+1. static (if applicable)
+1. final (if applicable)
+1. return type (methods only) or type (for variables)
+  The type is for readability as close as possible to the name.
+
+This order is also compatible with the order that is used in Java for the main() method. This results in following sequence:
+
+
+    // A familiar one:
+    public static void main(String[] args) {}
+    private static String m_lastCreated = null;
+    private static final int RED = 4711;
+
+
+#### Number per line
+
+One declaration per line is recommended since it encourages commenting and it does not lead to confusing code. It also is more clear about the explicit initialization of variables as discussed in Initialization.
+
+Example:
+
+
+    int level = 0;           // level where user enters the system
+    int horizontalSize = 0;  // horizontal size of current level layer
+
+
+is preferred over:
+
+
+    int level, horizontalSize; // level and size of current level layer
+
+
+#### Placement
+
+In a method, declare local variables just before they are needed. This overcomes the problem of a big list of parameters at the beginning of a method and the use of a variable becomes more clearly in the context of the code, .e.g. its initialization.
+
+#### Initialization
+
+The initialization of class variables is strictly not necessary because of the default initialization that takes place for these kinds of members. For some types, e.g. Booleans, this requires detailed knowledge of all the default values so it is more clear and explicit to initialize each member. 
+Variables that are used and declared within methods must always be initialized explicitly (the compiler will generate an error when you forget this).
+
+#### Class and Interface Declarations
+
+When coding Java classes and interfaces, the following formatting rules should be followed:
+
+- no space between a method and its parameter list
+- "\{" is on a line by itself indented to match its corresponding opening statetment, except when it is a null statement, in which case the "\{" should appear on the same line as the opening statement
+- "}" starts a line by itself indented to match its corresponding opening statement, except when it is a null statement, in which the case the "}" should appear immediately after the "\{".
+
+Example:
+
+
+    class ShipmoTrial extends Trial
+    {
+        int m_index = 0;
+    
+        ShipmoTrial(int index)
+        {
+            m_index = index;
+        }
+    
+        void emptyMethod() {}
+    }
+
+ 
+### Statements
+
+#### Simple statements
+
+Each line should contain at most one statement.
+
+Example:
+
+
+    // Do not use this
+    argv++; argc++;
+
+
+#### Compound statements
+
+Compound statements are statements that contain lists of statements enclosed in braces ("\{...}"):
+
+- The enclosed statements should be indented one more level than the compound statement.
+- The opening brace should be at the end of the line that begins the compound statement; the closing brace should begin a line and be indented to the beginning of the compound statement. 
+- Braces are used around all statements, even single statements, when they are part of a control structure, such as a if-else or for statement. This makes it easier to add statements without accidentally introducing bugs due to forgetting to add braces. 
+
+#### if, if-else, if else-if else statements
+
+There are a lot of nested possibilities for if-else constructions. All these variations can be programmed in very cryptic ways that easily and often will lead to buggy code. By being more explicit in the used coding style a lot of confusion can be taken away.
+
+Note: When using only one statement in a compound block brackets are optional. It can be a good practice to use always brackets because mistakes can be made easily when adding a second statement and brackets are forgotten.
+ 
+The following example illustrates the correct use of brackets in a few different if-then-else constructions:
+
+
+    if (condition)
+    {
+        statement1;
+        statement2;
+    }
+    else
+    {
+        statement3;
+    }
+    
+    if (condition)
+    {
+        statement1;
+        statement2;
+    }
+    else if (condition1)
+    {
+        statement3;
+        statement4;
+    }
+    else
+    {
+        statement5;
+        statement6;
+    }
+
+
+Note that in the example the else if construction is started at a new line so the statement can not be overlooked.
+ 
+#### switch
+
+When using a switch statement use following guidelines:
+
+- Every switch statement should include a default case. The break in the default case is redundant, but it prevents a fall-through error if later another case is added. 
+- The so-called fall-through construction should be avoided. Only when there are good reasons to use it, make sure that  it is very clear that a fall-through is used (comment it).
+ 
+The next example shows the sample code that uses the guidelines for a switch statement:
+
+
+    switch (condition)
+    {
+        case A:
+            statements;
+            // falls through here!!
+        case B:
+            statements;
+            break;
+        default:
+            statements;
+            break;
+    }
+
+
+#### try - catch
+
+A try - catch statement should have the following format:
+
+
+    try
+    {
+        statements;
+    } 
+    catch (ExceptionClass ex)
+    {
+        statements;
+    }
+
+
+When using finally to add code that always will be executed this will look like:
+
+
+    try
+    {
+        statements;
+    }
+    catch (ExceptionClass ex)
+    {
+        statements;
+    }
+    finally
+    {
+        statements;
+    }
+
+
+Note that the catch and the finally start at a new line in order to be compliant to the guidelines for if-then-else statements.
+
+### White Space
+
+#### Blank lines
+
+Blank lines improve readability by setting of sections of code that are logically related.
+
+Two blank lines should always be used in the following circumstances:
+
+- between class and interface definitions;
+- between a group of methods that belong together (by its functionality or because they are part of the same interface).
+
+One blank line should always be used in the following circumstances:
+
+- between methods;
+- before a block or single line comment;
+- between logical sections inside a method to improve readability.
+
+#### Blank spaces
+
+Blank spaces should be used in the following circumstances:
+
+- A keyword followed by a parenthesis should be separated by a space.
+
+    while (ready == false)
+    {
+    	...
+    }
+
+Note that blanks should not be used between a method call and its opening parenthesis. This helps to distinguish keywords from function calls.
+- Blanks should appear after commas in argument lists.
+- All binary operators except "." should be separated from their operands by spaces. Blanks should never separate unary operators such as unary minus, increment("++") and decrement("--") from their operands.
+
+    a += c + d;
+    a = (a + b) / (c * d);
+    xCoord++;
+
+- The expressions in a for statement should be separated by blanks.
+
+    for (expr1; cond1; expr2)
+
+- Casts should be followed by a blank.
+
+    myInstance.doIt((TreeFrame) frame);
+
+
+### Naming conventions
+
+Naming conventions make programs more understandable by making them easier to read. They can also give information about the function of the identifier.
+
+|Identifier Type|Rules for Naming|Examples|
+|--|--|--|
+  
+  
+|Interfaces|Interface names should be capitalized like class names.|interface Enumeration;|
+|Methods|Methods should be verbs in mixed case with the first letter lowercase. Within each method name capital letters separate words. Property methods or get-set methods are used as follows:
+  
+  
+  
+  
+  
+  
+|Constant (static final) variables|Names should be all uppercase with words separated by underscores ("_").|public static final int BLACK = 99;|
+|Exceptions|Like class names; always ending in "Exception"|InputException|
+|Packages|Lowercase only; avoid lengthy package names; always start with org.apache.felix.|org.apache.felix.demo.bundle|
+
+Note: All Java identifiers are case sensitive.
+
+## References
+
+- Java Code Conventions - Sun Microsystems, Inc.
+  No ref. number, only hyperlink: http://java.sun.com/docs/codeconv/
+- How to Write Doc Comments for JavaDoc - Sun Microsystems, Inc.
+  http://java.sun.com/products/jdk/javadoc/writingdoccomments.html
+- JavaDoc homepage - Sun Microsystems, Inc.
+  http://java.sun.com/products/jdk/javadoc/
+- [Eclipse formatting template](https://issues.apache.org/jira/secure/attachment/12419890/Apache+Felix+Eclipse+Template.xml).
\ No newline at end of file

Added: felix/site/trunk/content/documentation/development/committers.mdtext
URL: http://svn.apache.org/viewvc/felix/site/trunk/content/documentation/development/committers.mdtext?rev=1421893&view=auto
==============================================================================
--- felix/site/trunk/content/documentation/development/committers.mdtext (added)
+++ felix/site/trunk/content/documentation/development/committers.mdtext Fri Dec 14 14:29:22 2012
@@ -0,0 +1,62 @@
+Title: Committers
+
+# Committers
+
+- Timothy Bennett
+- Noel Bergman
+- Derek Baum
+- Humberto Cervantes
+- Hiram Chirino
+- Chris Custine
+- Matteo Demuru
+- Pierre de Rop
+- Filippo Diotalevi
+- Didier Donsez
+- Juan C. Duenas
+- Clement Escoffier
+- Freeman Yue Fang
+- Stephane Frenot
+- Francesco Furfari
+- Göktürk Gezer
+- Ken Gilmer
+- Jamie Mark Goodyear
+- Richard Hall
+- Niclas Hedhman
+- David Jencks
+- Alex Karasulu
+- Peter Kriens
+- Trustin Lee
+- Stefano Lenzi
+- Berin Loritsch
+- Stuart McCulloch
+- Felix Meschberger
+- Tim Moloney
+- Guillaume Nodet
+- Marcel Offermans
+- Arjun Panday
+- Karl Pauls
+- Enrique Rodriguez
+- Jose L. Ruiz
+- Sanjeeb Kumar Sahoo
+- Sten Roger Sandvik
+- Manuel Santillan
+- Guillaume Sauthier
+- Dave Savage
+- Christian van Spaandonk
+- James Strachan
+- Xander Uiterlinden
+- Upayavira
+- Valentin Valchev
+- Gert Vanthienen
+- Rob Walker
+- Sylvain Wallez
+- Adam Wojtuniak
+- Carsten Ziegeler
+
+# How to get involved ?
+
+Do you want to take part in the development of Felix ?
+Well there are a number of things that can be done. 
+
+* First of all, subscribe to the Felix dev mailing list and participate there.
+* Add patches to issues in the issue management tool.
\ No newline at end of file



Mime
View raw message