In an ideal world, we would have a superpom referencing all the features artifacts new versions (possibly with auto incrementing while finding one on the maven repos), plus a battery of integrations tests that validate that versions (if it doesn't work, this test sends a mail to the incriminated artifact Author). I think this solution is feasible an can be a time saver on middle term.
In an other ideal world, Eclipselink feature remains to the Eclipse community, spring-data one to Spring, etc... But I really don't think that it is realizable as the majority of these communities aren't using Karaf. For the moment, I think that SMX is the right way to push features as it is mainly deserved to it (and bundlyfication). Concerning the presence of the manifest in my features, is it wrong to have more information about the project in its MANIFEST? I didn't specify any imports nor exports... -- View this message in context: http://karaf.922171.n3.nabble.com/New-Karaf-features-on-github-tp4027864p4027919.html Sent from the Karaf - User mailing list archive at Nabble.com.
