We have been discussing a similar topic within OSGi. What would be nice to have is a generic provide/requires mechanism that can be used to express these types of dependencies (non-java package dependencies). Another example of this issue is the SWT bundle. It cannot function without one of its platform specific fragments installed. But there currently is no declared dependency form the swt host bundle and its platform specific fragments. This means an SWT host will resolve and all other bundles that require org.eclipse.swt will be resolved and think they can function, but they will undoubtedly fail.
Wouldn't it be nice if the fragment could specify that it provides the
native code support for SWT and the SWT host could declare a requirement
for a native code provider.
Tom
From: Boris Bokowski <[email protected]>
To: E4 Project developer mailing list <[email protected]>
Date: 01/14/2009 11:24 AM
Subject: Re: [e4-dev] Dependency Preference and Versioning
Another issue that we need to consider is the non-Java parts that go into a
bundle and are not contained in a package. Isn't the rule that you need to
use Require-Bundle if you depend on things like extension points?
Also, making everything keyed off packages is very Java-centric - what
happens when I write a bundle containing JavaScript code?
Boris
Chris Aniszczyk wrote on 01/14/2009 09:26:02 AM:
> Have we had a 'sins of our past' discussion around dependency
> preferences? For example, since we are starting anew in e4, should
> we prefer Import-Package over Require-Bundle everywhere to promote
> looser coupling? Furthermore, do we want to prevent people from re-
> exporting dependencies?
>
> For versioning... if we prefer package-level versioning... do we
> want to evolve versions on a per-package basis or simply have
> package versions match bundle versions?
>
> I'm only bringing this issue up as we have a chance to revisit the
> way we do dependencies and version things. I know there's many cases
> currently in the SDK where we have regretted either re-exporting a
> bundle (e.g., org.eclipse.ui mess) or versioning something improperly.
>
> Thoughts?
>
> Cheers,
>
> ~ Chris
>
> _______________________________________________
> e4-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/e4-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
