Re: [cross-project-issues-dev] Orbit Bundles To Be Removed From 2018-09

[Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>]

Hi Ed,

> IMHO this means that Code Recommenders must withdraw from SimRel.
> 
> a) all SimRel contributions should use the latest Orbit version

yes, but the emphasis is on *should*.

> b) mismatch of Guava has been a long-running nightmare with Guava
> classes in APIs a known no-no causing projects that integrate diverse
> Guava contributions to fail with bad classes.

As I said last year on this list, the problems show up only if you
expose Guava in your external API and do not have uses constraints in
place. Once you do the latter, you won't see LinkageErrors or similar
problems. It does mean, however, that if your clients use Guava, then
they must use the same version as you. That's the price you have to pay
for using Guava (directly or indirectly) in your external API.

At any rate, the mere presence of another bundle (unless it does some
arcane reflection/class-loading hackery, which AFAICT Guava does not)
should never break your bundle unless your metadata (version ranges and
uses constraints) is not in order. That's the whole point of OSGi:
Different bundles can use different versions of the same library in the
same runtime.

Best wishes,

Andreas

-- 
Codetrails GmbH
The best code possible

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

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

Attachment: signature.asc
Description: OpenPGP digital signature