On 09-05-12 11:25, Balázs Zsoldos wrote:
Hi,
thank you again for the detailed answer.
I don't think there is any justification for blessing either of these as
a "Best Practice", since it depends on your use cases.
I must disagree. I think if developers get free hand in situations like
this it will really hit back in a longer period. Now as OSGI is imported
into all major Java EE application servers OSGI is just before a big
explosion (similarly when suddenly many projects went from ANT to Maven
as a compilation tool). More specifically the explosion has already been
started. Without strict rules in this questions and building up
dependency management repositories (like maven or P2 update sites) based
on these rules will make developers suffer (working at night to find out
what went wrong) a lot in the future.
The purest way should be chosen and the one that makes the highest
concistency between the bundles.
I must say I agree with Neil, it entirely depends on your use-case.
And 'purest' is all a matter of perspective.
Also, I too believe OSGi is booming and OBR is the specification aimed
at facilitating easier dependency management.
--
Ferry Huberts
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
