Hi, > yes, see SLING-6043. > > Additional benefit is the reusability of configurations. Thanks for the reply. I've checked the issue and it seems to be fixed in Karaf 4.2.0 [1]. Since Sling Karaf use features schema 1.5.0 that is only available in 4.2.0+ I think configurations can be inline safely.
I'm not convinced about the re-usability argument. Is this a real use case that was found in practice or is it more of a theoretical re-usability. I'm inclined to think it's the second, in which case having two projects makes updating tedious. Internally I'm going to use the inline approach since I don't see any benefits in re-usability. If there will be such a use case I will gladly switch without looking back. However, in my use cases, I found that having the config project leads to maintenance burden (code bureaucracy :) ). [1] https://issues.apache.org/jira/browse/KARAF-4346 / Eugen
signature.asc
Description: OpenPGP digital signature
