Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Still issues with multiple Guava versions ... still time to fix them

On 2014-06-02, 5:31, Ed Willink wrote:
a) Guava must not be exported and so avoid OSGI class loader confusion.
- API tooling could warn if any non-singleton plugin is exported.

b) Requirements to load Guava classes must not be exported
- API tooling could warn if a class in a non-singleton plugin is
externally class loadable

It's Monday morning and I certainly didn't get enough caffeine in my
bloodstream yet, but I don't see the difference between these two
points. Can you explain what you mean by "externally class loadable" and
how it is different from OSGi Export-Package?


Back to the top