[SLING-6048] Sling Models: Automatic Registration of Sling Models via bnd Plugin

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Sling Models bnd Plugin 1.0.0
• Component/s: Extensions
• Labels: models
• Assignee: Stefan Seifert
• Reporter: Stefan Seifert
• Created: 09/Sep/16 11:52
• Updated: 20/Nov/16 21:13
• Resolved: 20/Nov/16 21:13

Description

currently, packages with sling model classes have to be registered with a Sling-Model-Packages bundle header. when such a bundle is deployed the classpath gets scanned and all models of this package (or subpackages) is registered. the developer has to add this header manually to his bundle (e.g. via pom/maven-bundle-plugin).

we should additionally provide an alternative for model class registration:

• introduce a new header Sling-Model-Classes which lists all class names with sling models
• when such a bundle is deployed both headers are supported. for bundles with only Sling-Model-Classes no class path scanning is required.
• we add a bnd plugin which scans the project class files on compile time for classes with sling model annotations, and automatically add fills the Sling-Model-Classes header
• thus when using this bnd plugin no manual configuration of any bundle header is required
• the bnd plugin should work with both maven-bundle-plugin and bnd-maven-plugin (or when using bnd directly)

this approach is quite similar as recently discussed in SLING-6025

Issue Links

• relates to: SLING-6308 Support Sling-Models-Classes bundle header