> what is missing from maven is the ability to communicate arbitrary > custom attributes > on per-dependency basis, such as: > > provide osgiStartLevel value, to specify to osgi runtime bundle start level: ... > or provide karafBootInstall flag, to specify that karaf runtime should > install this dependency at boot-time vs build-time: ... > in lieu of these, karaf-maven-plugin is trying to encode this > information via <scope> > https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215 > > which contradicts the dependency resolution rules and really does not work. > > hence my request to "relax". is there any other ways to address this need?
IMO this can and should all be handled via configuration in the karaf-m-p and not via adding attributes in dependencies which are specific to one plugin. Otherwise the Assembly plugin could reasonably ask to put "outputFileNameMapping" as an (optional) attribute of the dependency, and the Ear plugin could ask to put "bundleFileName" as an (optional) attribute, etc. That way lies madness. Look at how Assembly and Ear plugins (and others) are doing similar things for guidance on how to implement these features in the karaf plugin itself. FWIW I agree that doing it via <scope> is the wrong way to do it. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
