I tried to import just p2.core and p2.repository and the compilation issues are gone.
Despite that, I’m not sure it is enough to validate that the issue is related to p2 psf. I looked at the psf files but didn’t find which one should be updated or deleted.
If you think it makes sense to perform more precise validation and provide some steps how to do so, I could check again.
Thank you for the help,
Katya
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Matthew Piggott
Sent: lundi 11 juillet 2011 18:12
To: P2 developer discussions
Subject: Re: [p2-dev] Pending patches in preparation to Git move
I added this to the bug, but it appears that the problem may be due to a project that isn't part of the p2 psf. The project org.eclipse.equinox.p2.repository.impl has the name "org.eclipse.equinox.p2.repository" and attempts to import old packages which have been moved. This also prevents the real org.eclipse.equinox.p2.repository from being imported, maybe double check to see if this was the problem you encountered.
Matthew
On 11/07/2011 9:25 AM, Todorova, Katya wrote:
I used this bug to continue investigation:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=345474
Thanks,
Katya
As of now I believe that repo is the test repo for the p2 migration. Although if you are seeing strangeness with it then it may indicate a problem encountered when they did the test migration to create the repo.
Tom
"Todorova, Katya" ---07/11/2011 06:36:41 AM---Guys,
Guys,
Is git.eclipse.org/gitroot/equinox/rt.equinox.p2.git supposed to be ready to use?
I tried cloning it and the operation seems to finish successfully but afterwards most of the projects (when imported in Eclipse) don’t compile properly.
For example p2.repository doesn’t see some of the exported packages by p2.core.
Any idea what’s wrong?
Thanks,
Katya