The Sling 11 release adds better support for present and future Java versions, upgrades to the latest stable Oak and OSGi specification releases and features improved ACL setup for out-of-the-box.
To find out more about running Sling, see our getting started page.
Sling 10 worked just fine on Java 9 or newer but required the addition of the --add-modules java.se.ee flag. This is no longer needed, and Sling is validated to work on all Java versions from 8 to 11.
We use the latest stable Oak version from the 1.8 stream, bringing in over 1200 fixes and improvements. See the full list of resolved issues for Oak 1.8.0 to 1.8.8.
The Config Admin, SCR, Event Admin, Metatype and HTTP bundles are now at the R7 level. These updates bring numerous improvements and fixes, such as:
For more details, see A summary of the OSGi r7 release.
The 1.4 version of the HTML Template Language Specification brings the following enhancements:
uridisplay context is applied automatically
For more details, see the HTL 1.4 release
The Sling Starter application now installs all content under
/content/starter to prevent clashes with other applications.
Moving all content under
/content has made it possible for the Sling Starter to have a more secure setup out-of-the-box, where only
/content is accessible to unauthenticated users.
Repoinit, the repository initialisation language, has received a number of enhancements:
See the repoinit documentation for more details.
The Web Console and regular Sling login experiences have been unified, and if a user accesses the web console without being authenticated the configured Sling login mechanism is used. By default this mechanism is the form-based one.