Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344936

Summary: "MD5 hash is not expected" when downloading from Jetty 7.x p2 repository
Product: [RT] Jetty Reporter: Rüdiger Herrmann <ruediger.herrmann>
Component: buildAssignee: Jesse McConnell <jesse.mcconnell>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: hmalphettes, jetty-inbox, ruediger.herrmann
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Screenshot none

Description Rüdiger Herrmann CLA 2011-05-06 05:19:58 EDT
Steps to reproduce (with a fresh Eclipse 3.6 SR2 install and a new workspace):
1. go to Preferences -> Target Platform
2. select "Add"
3. in the upcoming "Taret Definitin" dialog, press next
4. then Add
5. in the "Add Content" dialog, select "Software Site"
6. then enter the URL http://download.eclipse.org/jetty/updates/jetty-bundles-7.x/
7. and select both features (Jetty - Bundles: all the Jetty bundles and ... sources)
-> adding the bundles to the atarget fails with "MD5 hash is not expected" (I will provide a screenshot)
Comment 1 Rüdiger Herrmann CLA 2011-05-06 05:20:19 EDT
Created attachment 194913 [details]
Screenshot
Comment 2 Hugues Malphettes CLA 2011-05-06 07:58:46 EDT
Thanks for taking the time to explain where the issue is happening.
I suspect the signing part of the jetty-bundles build.
The milestones are not built with the same version of the maven plugins and that is why it works over there and not for the jetty-bundles.
Comment 3 Jesse McConnell CLA 2011-05-10 17:32:23 EDT
we are close to getting the signing plugin into dash so we'll be able to spruce it up and use it across more builds then just our handful...

these older builds we might just kiss off as dead once we use the new plugin but we'll see how it falls out..I'll keep this issue updated as we progress through
Comment 4 Jesse McConnell CLA 2011-07-19 15:20:15 EDT
new plugin is in dash now and I believe all the latest builds are working correctly

if this remains an issue please reopen and we'll investigate further and smoke any buglets