Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mpc-dev] outdated repository at

Thanks Nathan! It is working for me now.

Adding the p2.index file is an (optional) optimization that gives p2 a
hint which files to download:

 347448: Add p2.index in indigo repos

If the p2.index file is not present p2 will make requests for
content.jar and content.xml which will result in 404s before it finds
the compositeContent.jar.

It's a small gain but it's easy to do and low risk. I would recommend doing it.


On Wed, Jun 22, 2011 at 5:21 PM, Nathan Gervais <nathan@xxxxxxxxxxx> wrote:
> Steffan,
> I've removed content.xml from that location.
> I've also asked about whether the files i have in that directory need to be
> updated as well in
> Can you expand on what you meanFor the p2.index file?  I'm not sure what
> your asking me to do there.
> Nathan Gervais
> Web Developer - Eclipse Foundation
> On 6/22/2011 11:04 AM, Steffen Pingel wrote:
>> While testing I noticed that the
>> /home/data/httpd/ has outdated
>> meta-data that references IUs from an Indigo milestone build rather
>> than the final repository contents.
>> This causes installs to fail with errors such as "No repository found
>> containing: osgi.bundle,org.eclipse.birt.core,3.7.0.v20110519".
>> It seems that the content.xml should be deleted ASAP so that p2 uses
>> the compositeArtifacts.jar and compositeContent.jar instead.
>> We should also place a p2.index file in the same directory to avoid
>> unnecessary round-trips:
>> version=1
>> metadata.repository.factory.order=compositeContent.jar,!
>> artifact.repository.factory.order=compositeArtifacts.jar,!
>> Steffen
> _______________________________________________
> mpc-dev mailing list
> mpc-dev@xxxxxxxxxxx

Steffen Pingel
Senior Developer,

Back to the top