Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Guava 15/21 warning


> If you have a technical solution that allows multiple Guava versions to
> co-exist, please add it to Bug 437107. My current understanding is that
> "uses" directives may be a solution but that no demonstration has been
> performed and so the requirements for tooling are at best guesses and of
> course not yet implemented. It is unlikleyt that any project currently
> complies with any potential "uses" solution.

not true. Code Recommenders has exported interfaces [1] which have Guava
classes in their public signature. However, Code Recommenders [2]
properly declares these uses constraints and has not seen a major
problem since we introduced this in 2013(!).

Yes, if consumers of the org.eclipse.recommenders.models API also want
to use Guava for other purpose, then they are restricted in their choice
of Guava versions by what org.eclipse.recommenders.models uses but
that's how OSGi works.

This is IMHO a small price to pay for generally being able to have two
versions of the same bundle in your runtime. No more "one classpath to
rule them all", which *might* work in the closely coordinated
simultaneous release (although based on [3] I doubt it), but certainly
not once third-party plug-ins come into play.

Best wishes,



Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

Attachment: signature.asc
Description: OpenPGP digital signature

Back to the top