Also using Import-Package allows for provider substitution. You don't really know who the provider of the package dependency is by looking at a bundle manifest in isolation.
Tom
Wayne Beaton ---05/17/2013 02:06:35 PM---The issue is one of tracking who is using what third-party library. Right now, the tools that I use
From: Wayne Beaton <wayne@xxxxxxxxxxx>
To: cross-project-issues-dev@xxxxxxxxxxx,
Date: 05/17/2013 02:06 PM
Subject: Re: [cross-project-issues-dev] Libraty piggy-back CQs
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
The issue is one of tracking who is using what third-party library.
Right now, the tools that I use to scan the downloads directory almost do a good enough job to eliminate piggyback CQs altogether. Almost. The problem is that the tool only detects libraries that are actually distributed by the project. It works by file name alone. It fails to detect libraries that are pulled in from Orbit, for example.
I think that the solution is to scan bundles for references to third-party libraries, but I'll need some p2 magic to sort that out, I think. Bash just isn't going to cut it.
Does anybody know what p2 magic we can use to query a bundle for a definitive list of dependencies (including bundle and package imports?)
Of course, this doesn't help us if a project isn't distributing OSGi bundles...
Wayne
On 05/17/2013 02:35 PM, Ed Willink wrote:
--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
Learn about Eclipse Projects
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|