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

Bug 403597

Summary:	4.3M6 p2 repository metadata not jar'ed
Product:	[Eclipse Project] Platform	Reporter:	Jan Sievers <jan.sievers>
Component:	Releng	Assignee:	David Williams <david_williams>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	david_williams
Version:	4.3
Target Milestone:	4.3 M7
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Jan Sievers

2013-03-18 04:30:15 EDT

I noticed Kepler M6 milestone repository

http://download.eclipse.org/eclipse/updates/4.3milestones/S-4.3M6-201303141330/

is not jar'ed (it uses content.xml and artifacts.xml)

Is that on purpose or a bug?

With content.xml uncompressed file size at 3.7 MB I guess it makes sense to jar the p2 index files to save some network bandwidth.

Comment 1 David Williams

2013-03-21 12:36:34 EDT

This is partially "our" fault because of work that Paul is doing in bug 394216, but, it reminded me to open bug 404053 since if the property was there in the repo, I think subsequent p2 operations would re-jar it.

Comment 2 David Williams

2013-05-07 20:33:13 EDT

We fixed "indirectly" in M7 -- at least for our production builds -- which is what ends up on .../updates/ URL.

If/when "indirect" part is ever removed/changed, I've added a reminder in bug 394216 to re-jar the file once tweaking is complete. 

Though to correct comment 0, even for M6, only content meta data was, unjarred, 'content.xml' ... the artifacts metadata was artifacts.jar.