Hey Fulco,
Short answer: The clean way to go here is to define all bundles
required in your features.xml. Everything else could generate a GREAT
mess, because (for example) not all deps have to be osginized, not all
deps import versions correctly (which leads to some problems since
transitive
Andreas,
Thanks a lot for the quick answer, I appreciate!
In a short time I guess I've no other choice to add all dependencies in the
features descriptions.
I understand that for a single custom bundle it's important to keep control of
all dependencies. However, for bigger projects like a
Well, there are two goals in the Karaf Maven Plugin which might do
what you want ([1] and [2]). Please check if they do what you like.
I've never used them but they should be able to automatically generate
the feature files including dependencies.
Kind regards,
Andreas
[1]
Note that those goals have some problems in karaf 2.x (not bugs, but
rather by design). This is being worked out for 3.x and
auto-generation of features descriptors should be much better.
On Fri, Jun 10, 2011 at 16:24, Andreas Pieber anpie...@gmail.com wrote:
Well, there are two goals in the
