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

Sorry, I lost track of the thread a bit. What's the conclusion? Should projects continue using 15.0.0 or upgrade to a more recent one?

Thank you,


From: cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>
Sent: Tuesday, March 14, 2017 11:55:26 AM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] Guava 15/21 warning
Hi Ed,

> Great, you sound like an expert who has demonstrated a solution.
> Can you contribute a wiki page on how you do it?

I'll try, although the PDE tooling isn't that great [1, 2]. IMHO, bnd is
far better at automatically identifying uses constraints (although you
can still cheat it by using reflection), but most Eclipse projects use
Tycho and manifest-first builds, so I guess that's what the Wiki page
should focus on.

FYI, if you don't mind (and the OCL Oomph setup is up-to-date) I may use
OCL as a running example.

> Can you identify what checks a SimRel report should do to detect
> projects that are doing it wrong?

I agree, reports would be great. I am not aware of any tooling for this,
though. The maven-bundle-plugin focuses on *generating* MANIFEST.MFs
with uses constraints rather than checking the uses constraints of
existing MANIFEST.MFs. Also, I don't think PDE has a tool that could
easily be turned in a manifest checker. :-(

Best wishes,


[1] <>
[2] <>
[3] <>

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

Back to the top