Community
Participate
Working Groups
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.
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?
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.
closing as per last comment.
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.