[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] BBAPI source code repository.
|
Hmm... I just checked out the whole project-set and I get a lot of
errors that classes in:
org.eclipse.ecf.core.util are not resolved. I think this is exactly
because two bundles are exporting the same package and Import-Package
will resolve to only one of them I think (I'm using 3.3M3 if that
makes a difference).
So perhaps it's not a good idea to use Import-Package everywhere? It
also makes it a pain when packages change and I think dependency
management becomes too granular. I've personally used Import-Package
when declaring dependencies on external libraries or on packages that
might be bundled differently depending on situation. Or when trying to
keep dependencies to a minimum. But when I know very well which bundle
should provide the packages, I usually use Require-Bundle. But I know
Peter Kriens from OSGi for example doesn't like Require-Bundle at all.
Maybe we could ask for advice from the Equinox team?
On 11/6/06, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Hi Erkki,
Cool...thanks!
BTW...over the weekend I moved all the core plugins to use
Import-Package rather than Require-Bundle. Among the new set of core
plugins there is now only *one* Require-Bundle...that's org.eclipse.ecf
requiring org.eclipse.ecf.identity. The reason I left that one is that
org.eclipse.ecf.identity and org.eclipse.ecf both contribute code to a
single package (org.eclipse.ecf.core.util), and so Require-Bundle is needed.
Scott
Erkki Lindpere wrote:
> During the ECF call, Scott asked where the BBAPI source code can be
> accessed. It is available here:
>
> http://bbapi.tigris.org/source/browse/bbapi/
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
