On 19.10.2016 16:57, Guillaume Nodet wrote:
Something like:
<bundle>mvn:...</bundle>
<bundle>mvn:...</bundle>
...
That sounds like a feature to me ;-)
The advantage would be that you can use IDE tooling for poms like M2E.
So you get search and completion for the artifacts. You get nice
introspection for the transitive dependencies.
I think one thing we are missing in karaf feature files is IDE support.
Anyway, a custom osgi resource repository can be easily created for an
external file by inheriting
org.apache.karaf.features.internal.repository.BaseRepository. Just add
your new repository into org.apache.karaf.features.internal.region.
getRepository and it should work.
Sounds interesting. I will play with that.
Again, in the simple cases, if this list of bundles can be generated, it
means that the feature itself can be generated, so I'm not sure where the
benefit is...
I have not used the generated features a lot. One thing that might be
problematic is that a feature file can contain several
features while a pom can only contain one list of bundles. That is why I
would treat the list of bundles from the pom rather as a
backing repository than as a feature.
Again I think the main benefit would come from tooling. Bndtools allows
to search in the index and just drag bundles into the requirements.
Such a mechanism would also be great for features. Unfortunately we do
not have a lot of good Eclipse RCP or Intellij plugin developers at Apache.
So I guess the dream of having decent IDE tooling is quite far away :-(
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
