[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] P2 Mirror Application fails to mirror Eclipse repo

My apologies for alarming you. I was looking at a mirror dir from an old test run.
I have now managed to successfully mirror both content and artifacts plus features and plugins from both the Eclipse and Ganymede repos. The mirrors do not seem to be perfect, however. Here are my results:
Eclipse Repo: http://download.eclipse.org/eclipse/updates/3.4/
artifacts expected: 1674
artifacts actual    : 1667
units (content) expected: 1373
units (content) actual    : 1359
ganymede Repo: http://download.eclipse.org/releases/ganymede/
artifacts expected: 1943
artifacts actual    : 1942
units (content) expected: 2436
units (content) actual    : 2436
I am adding a macro to my mirror script that tests the mirror once complete by comparing the expected vs actual artifacts and units. I think it would be a good idea to add such a test to the mirroring applications, which could be run optionally once the mirror op completes. What do you think?
Miles Daffin
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf | Floor 01
London, E14 4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572

From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Cattle
Sent: 26 November 2008 18:28
To: P2 developer discussions
Subject: RE: [p2-dev] P2 Mirror Application fails to mirror Eclipse repo

Now I'm really concerned...

Can you try manually running the metadata mirror into an empty folder? If you get a content.jar from that then you should be able to just copy and paste it into your target.

I wouldn't overwrite the target because you seem to have had a completely successful artifact mirror (congratulations!) and we don't want to wait for you to get another one of those.

This is a really tough problem because I can't seem to reproduce it. If the system wasn't trying to load the artifact data as a metadata repository then I currently have no clue what's causing your problem. I will continue to look into it.

Thank you for your patience.

NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.