Community
Participate
Working Groups
Build Identifier: M20090917-0800 I can't install AJDT because I'm getting the following error: An error occurred while collecting items to be installed session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=). Problems downloading artifact: org.eclipse.update.feature,org.eclipse.equinox.weaving,1.0.0.200906171200. MD5 hash is not as expected. Expected: f41047212a251de231e16cfb7e22073e and found a6db2b591cce057a7769bbbec4708ca2. Problems downloading artifact: org.eclipse.update.feature,org.eclipse.equinox.weaving.source,1.0.0.200906171200. MD5 hash is not as expected. Expected: 183fbeafea35f19f0a75bb6a7e66dfb1 and found dbac4a8daa4a240a1377777f17589c3f. Reproducible: Always Steps to Reproduce: 1. Window - Install new software 2. Choose http://download.eclipse.org/tools/ajdt/35/update as source 3. Select AspectJ Develelopment Tools
OK...please try again.
I had the same problem yestarday and it works now, thank you. I just get a warning that the jars are not signed. Btw, I couldn't get it to work from the zip also.
I had to update the jars for Equinox Aspects. Now that they are updated, it should be working fine. As for installing from zip, that requires a different method of install, but I am working on making it more automated.
Andrew, I'm having a similar problem with MD5 hash when mirroring from http://download.eclipse.org/tools/ajdt/35/update: Problems downloading artifact: osgi.bundle,org.eclipse.equinox.weaving.source,1.0.0.200906171200. MD5 hash is not as expected. Expected: 4000dfb1eb5359d14695f569ca97edda and found b24f40c0d7c3e1389c353f0c4056ef6a.
I am not able to reproduce this problem. I am able to install from the update site myself. It could be that one of the mirrors were down for a bit. Please try again. If you continue to see problems, then I'd suggest trying to install from the dev update site: http://download.eclipse.org/tools/ajdt/35/dev/update
Thank you for your help, Andrew. I should have been more specific about the problem: I was trying to mirror the p2 repository (with p2.mirror task), not to install from it. Strangely enough, it occurs that mirroring the repository fails all the time with the above-mentioned error about MD5 hash, while installing from the repository succeeds (as you said and I've just confirmed). I've tried to mirror the dev repository and it works, but I need to obtain a mirror of 2.0.2 repository, not 2.0.3.
It is very likely that the update site for 2.0.2 and less is not producing the correct MD5 hashes. Post 2.0.2, we have moved to a new build server and so it should work from now on. I do not think it will be possible to fix the MD5 hashes for the 2.0.2 release. For what purpose are you creating the mirror?