adaptTo() 2017 - Ease Development with Apache Sling File System Resource Provider

Code samples for talk at adaptTo() 2017 in Berlin:
https://adapt.to/2017/en/schedule/ease-development-with-apache-sling-file-system-resource-provider.html

Requirements

• Java 8
• Maven 3.3.9
• AEM 6.1, 6.2 or 6.3 running on port 4502

Try it out

• Deploy the sample application to your local AEM instance using the script clean_install_deploy_package.sh
  • This does a full mvn clean install and then uploads the content packages from content-packages
• Open the sample site at http://localhost:4502/editor.html/content/adaptto-fsresource-sample/en.html

Deploy Bundle

To deploy the OSGi bundle including the Sling Initial Content to the local AEM instance:

• Go to bundles/core and execute

mvn install sling:install

Enable File System Resource Provider

To enable the File System Resource provider for the OSGi bundle and sample content FileVault project:

• Go to bundles/core and execute

mvn sling:fsmount

• Go to content-packages/sample-content and execute

mvn sling:fsmount

• Change application content files in the bundle, or FileVault XML files in the sample content package. The changes are reflected immediately in the AEM instance.

Example Variants

There are two variants of this example:

• Simple variant (no extra bundles)
• Variant with i18n JSON files (extra Sling bundles deployed)

The variant with i18n JSON files takes a bit more time to deploy, because the Sling JCR Content Loader bundle has to be updated.