No repository found at

Trying to build local repository using p2:mirror which will be later used to build the product.

Using antRunner to build repository but getting error:

\eclipsec.exe -application org.eclipse.ant.core.antRunner -buildfile platform-builder.xml -Drepository=drep -Dsrc_repository=dsrc
Buildfile: platform-builder.xml

[echo] ------------------------------------------------
[echo] Mirroring linux,gtk,x86_64 platform
[echo] ------------------------------------------------

C:\work\temp\trunk\data\4.15\platform-builder.xml:30: The following error occurred while executing this line:
C:\work\temp\trunk\data\4.15\platform-builder.xml:57: The following error occurred while executing this line:
C:\work\temp\trunk\data\4.15\platform-builder.xml:228: org.eclipse.equinox.p2.core.ProvisionException: No repository found at
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.loadRepository(

This should work now, thank you for reporting this issue!

I still have the same problem building my Eclipse-RCP-application using maven-tycho:

Failed to load p2 metadata repository from location No repository found at -> [Help 1]

Same issue appears with the 1.8.x update site : when used in a Tycho build, Tycho can’t find it.
I think this is due to a mis-publishing of the update site.
Please, could you check whether you used the update site publisher application as described on :
and tell us if that’s the case ?

Thanks in advance.
PS : Note that on the other hand, the update site is correctly seen when trying to update from an Eclipse installation.

The problem is that the SVNKit update sites ATM use the old (as in 2009) pre-p2 update site format, i.e., just a plain site.xml without any p2 metadata (content.jar, artifacts.jar) needed by Tycho. See this Stackoverflow question for more context.

Would be great if the SVNKit update sites could be enhanced that way (not just for 1.10.x but also older sites, as, e.g., Subclipse sometimes declares rather narrow dependency ranges). The publish-features-and-bundles goal may be useful here.