[ https://issues.apache.org/jira/browse/SLING-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Edelson updated SLING-6048: ---------------------------------- Fix Version/s: (was: Sling Models Impl 1.4.0) > Sling Models: Automatic Registration of Sling Models via bnd Plugin > ------------------------------------------------------------------- > > Key: SLING-6048 > URL: https://issues.apache.org/jira/browse/SLING-6048 > Project: Sling > Issue Type: New Feature > Components: Extensions > Reporter: Stefan Seifert > Priority: Minor > Labels: models > Fix For: Sling Models BND Plugin 1.0.0 > > Attachments: add-classes-header.diff > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)