Hi Currently we create our launchers using the maven assembly plugin.
I see the following advantages of our approach: - Version of artifacts using maven mechanism (dependency management, IDE support) - Mvn URIs for bundle allowing easy updates from maven repo And disadvantages: - It's not possible to have list of the bundles for particular features - configuration quite hard An alternative would be the sling launchpad plugin Advantages: - Partial bundle lists to group features - Used in Stanbol and Sling allowing to mix and match partial bundlelists with these projects Disadvantages - unresolvable sling-uris for bundles - propertary bundlelist format not offering the same comfort as maven dependencies Yet another approach would be to create a launcher using Karaf Advantages: - Integrates with many karaf based applications - Karaf feature sets can be created from maven dependencies - Features can be added at runtime Disadvantages: - A Karaf distribution is not a self-executable jar - Compatibility issues to investigate, notably with regards of authentication/JAAS policy and the clerezza shell Just what came to my mind, thoughts would be greatly appreciated. Cheers, Reto
