On Sun, 2020-05-31 at 16:42 +0200, Konrad Windszus wrote: > Hi, > I recently integrated > https://github.com/bndtools/bnd/tree/master/maven/bnd-resolver-maven-plugin > in the FileVault plugin [1] and I would propose to do something > similar for Sling. > > That way incompatibilities of bundles would be more visible (and not > only once you integrate those in the starter). The whole resolve > process [3] would then be performed during the Maven build/ > For that it would be very helpful if we can generate a bundle index > [2] from all bundles in the starter ( > https://github.com/bndtools/bnd/tree/master/maven/bnd-indexer-maven-plugin > ), so that all necessary metadata is available. > Then we can even have multiple indexes (i.e. Sling 11, Sling 12, AEM > 6.5) for providing target environments for multiple different > distributions and decide per bundle with which distribution it should > be compatible. > > WDYT?
+1, would be interesting data to have. Thanks, Robert > > Konrad > > [1] - > https://github.com/apache/jackrabbit-filevault/commit/b8e952da80cf3a3cabd8fda6f89d0ed1b797cfb5 > [2] - > https://github.com/bndtools/bnd/pull/4078#issuecomment-634194422 > [3] - https://enroute.osgi.org/FAQ/200-resolving.html >
