No repository found at http://dist.springsource.org/release/GRECLIPSE/2.9.2/e4.4

Since today I’m getting the following error when trying to compile the smarthome project:

[ERROR] Failed to resolve target definition /Users/mad/Documents/openhab_workspace/openhab2/TheNetStriker/openhab2-master/git/smarthome/targetplatform/smarthome.target: Failed to load p2 metadata repository from location http://dist.springsource.org/release/GRECLIPSE/e4.4/: Unable to read repository at http://dist.springsource.org/release/GRECLIPSE/e4.4. No repository found at http://dist.springsource.org/release/GRECLIPSE/2.9.2/e4.4. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException

It seams as one or the repositories is no longer online. How can I fix this problem?

It appears smarthome hasn’t had any commits within the timeframe under discussion, so this is likely just a transient network error. AFAIK, the only thing you can do in these cases is wait.

I’m getting a slightly different error:

[INFO] Adding repository http://dist.springsource.org/release/GRECLIPSE/e4.4
[ERROR] Failed to resolve target definition \openhab2-master2\git\smarthome\targetplatform\smarthome.target: Could not find “org.codehaus.groovy23.feature.feature.group/2.9.1.xx-201411061335-e44-RELEASE” in the repositories of the current location -> [Help 1]

I fixed the problem by changing the targetplatform/smarthome.target file like this:

.....
<location includeAllPlatforms="false" includeConfigurePhase="false" includeMode="planner" includeSource="true" type="InstallableUnit">
<unit id="org.codehaus.groovy23.feature.feature.group" version="2.9.2.xx-201801041714-e47-RELEASE"/>
<repository location="http://dist.springsource.org/release/GRECLIPSE/e4.7/"/>
</location>
.....

The problem has been fixed.