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

Bug 351698

Summary:	Tycho doesn't like jar:/url/to/file.zip!/ in a .target file, whereas Eclipse supports such repositories
Product:	z_Archived	Reporter:	Mickael Istria <mistria>
Component:	Tycho	Assignee:	Jan Sievers <jan.sievers>
Status:	CLOSED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3	CC:	jan.sievers, vincent.guignot
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Mickael Istria

2011-07-11 07:27:33 EDT

Working with a .target file that contains a p2 repository in a ZIP file works in Eclipse, but Tycho fails to resolve the repository.
Example of URL: jar:https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp.inc-sieditor/lastSuccessfulBuild/artifact/development/org.eclipse.wst.sse.sieditor.repository/target/site_assembly.zip!/

[INFO] Adding repository jar:https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp.inc-sieditor/lastSuccessfulBuild/artifact/development/org.eclipse.wst.sse.sieditor.repository/target/site_assembly.zip!/
[WARNING] Failed to access p2 repository jar:https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp.inc-sieditor/lastSuccessfulBuild/artifact/development/org.eclipse.wst.sse.sieditor.repository/target/site_assembly.zip!/, will try to use local cache. Reason: org.eclipse.equinox.p2.core.ProvisionException: Communication with repository at jar:https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp.inc-sieditor/lastSuccessfulBuild/artifact/development/org.eclipse.wst.sse.sieditor.repository/target/site_assembly.zip!/ failed.

Comment 1 Jan Sievers

2011-07-11 08:24:07 EDT

AFAIK the underlying jar URL protocol in the JDK only supports jar:file URLs, not jar:http or other.

Can you confirm that installing/updating  from the jar:https URL into eclipse using the p2 UI works?

Comment 2 Mickael Istria

2011-07-11 08:37:59 EDT

I succesded to get it working when defining a target platform, but I do not succeed to reproduce that successful case. I assume that it was a case where the target platform editor silently made some magic to get the zip.

Nevermind, I understand that it is a JVM limitation, then I let you close the bug.

Comment 3 Jan Sievers

2011-07-11 09:49:53 EDT

closing as per last comment.

Comment 4 Mickael Istria

2011-07-11 11:52:12 EDT

Actually, I just had this use case of jar:https://....zip!/ working on our CI server!
Seems like Tycho and Eclipse support this kind of URLs, the problem was maybe because build was occuring at a wrong time.