Hi Koen ,),
What we did when cleaning up the exadel source code base was to follow the rule of thumb:
If your public API exposes API from another plugin you would reexport it, otherwise no.
I remember we found that somewhere on eclipse.org
as their golden rule too...but can't
remember where ,)
(for some reason koen gets emails but cant send to the list...working
on that, but in the meantime here is his mail)
Do we have a policy regarding exporting dependencies of a plugin to
possible extenders of this plugin? Or do we expect extenders to include
the dependencies themselves in their extensions?
plugin A depends on:
plugin B depends on
plugin C depends on
The way this can be tackled AFAIK is
- including the dependencies of B and C in extenso in the manifest file
- exporting the dependencies of plugin A on plugin 1 and plugin 3 and
only including a dependency on plugin A in plugin B and plugin C
Do we have a preferred way?
jbosstools-dev mailing list
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/