- we would like to switch completely to bnd-maven-plugin, but without the need for a separate bnd file - we currently have only one parent pom for bundle modules and non-bundle modules, making it difficult to configure the bnd-maven-plugin globally so it gets up picked only for bundles, not for simple jar files. - using maven profiles would be an option, but there is no nice way to trigger the profile without ugly hacks like having an empty bnd file present. - https://issues.apache.org/jira/browse/MJAR-193 would be another solution (haven the bnd plugin handing over the manifest extensions to the maven jar plugin), but this feature is not available yet
- the best solution seems to be to create an additional "sling-bundle-parent" inheriting from the existing "sling-parent" - all bundle-related stuff goes there and will be removed from "sling-parent" - old maven-bundle-plugin should be removed from sling-parent - maven-bundle-plugin should be banned from sling-bundle-parent - one repo for both, always released together - start with next version 36 - make a wiki page with migration steps - bundle modules will use "sling-bundle-parent", jar modules "sling-parent" we will do a vote on this. stefan
