| 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
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev