[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] 3.5 M5 migration issue
I don't know about the native call, but I can offer some advice on the queries.
We are trying to move away from collectors (more work in 3.6) in favour of more advanced queries. The reason for this is that repository implementors could potentially optimize queries based on their repository implementation. For example, get latest version, could be a quick query if the repository stored all the IUs in sorted order based on their version.
We would like to remove the requirement that collectors *must* be returned, and those implementing IQueryables could return their own collectors (possibly based on Futures or some other lazy loading technology). For more information on this, see .
As for the URL thing, you should be using URIs now.
On Wed, Mar 11, 2009 at 11:13 AM, Haigermoser, Helmut <Helmut.Haigermoser@xxxxxxxxxxxxx>
Ciao Guys :)
I was wondering if you could help me with a migration issue I'm seeing
with our previously 3.4-based installer.
At some point in the installation process I reach a native call which
does not return:
The native call is UnixProxyProvider.getGConfProxyInfo(String) (this is
The p2 version I'm using is the I-build of this week, same is true for
Also, in the past we were using Collectors a lot, as well as the
MetadataRepositories class that was fed some URLs,
looks like these concepts are not to be used anymore, Collector is not
derived more then 10 times anymore, and MetadataRepositories cannot be
fed URLs so easily anymore, do you have some pointers for alternatives?
E.g, I'm guessing that one should favor overriding the IMatchQuery base
classes instead of putting logic into Collectors?
P.S.: I could help write a migration guide, using my experience there,
if you could use that info?
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484http://eclipsesource.com