On 11/3/10 15:06, Bruno Rosell i Gui wrote:
Hi!
Require-Bundle with reexport visibility is a pretty bad practice...
Why? If you do not use it for a bundle that depende of any bundle you have to
add they dependencies, and the dependencies of the dependencies,and teh
dependencies of teh dependencies of teh dependencies,... so define a bundle is
too dificult, no?
That is not why reexport visibility exists...actually, I'm not sure why
it exists at all...I can't remember the argumentation for that one.
The only real reason to use Require-Bundle at all is if you have to deal
with split packages and even then you should avoid split packages, since
they are bad practice too.
You should use Import-Package to declare what your bundle actually
needs, which makes the bundle usable in more situations since you don't
depend on specific providers. Additionally, you can use tools like bnd
or maven-bundle-plugin to generate this information.
Using Require-Bundle often leads to a large fanout of dependencies.
Reexport visibility makes things worse, since it exposes everything to
downstream clients whether they want access to it or not. It tightly
couples everything together, since you don't know who depends on what
and it exposes all downstream clients to changes in the export signature
of upstream providers.
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
