build war is broken by artifact repository

[stefanocudini]

i am using docker hub image 6.3.6 which suddenly seems plagued with this problem.

from which docker version was the problem solved?

Failed to transfer file http://repo.heigit.org/artifactory/main/com/github/GIScience/graphhopper/graphhopper-core/v0.13.10/graphhopper-core-v0.13.10.pom with status code 308

98104 [ERROR] Failed to execute goal on project openrouteservice: Could not resolve dependencies for project org.heigit.ors:openrouteservice:war:6.3.6: Failed to collect dependencies at com.github.GIScience.graphhopper:graphhopper-core:jar:v0.13.10: Failed to read artifact descriptor for com.github.GIScience.graphhopper:graphhopper-core:jar:v0.13.10: Could not transfer artifact com.github.GIScience.graphhopper:graphhopper-core:pom:v0.13.10 from/to HeiGIT main (http://repo.heigit.org/artifactory/main): Failed to transfer file http://repo.heigit.org/artifactory/main/com/github/GIScience/graphhopper/graphhopper-core/v0.13.10/graphhopper-core-v0.13.10.pom with status code 308 -> [Help 1]
98111 [ERROR] 
98112 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
98112 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
98112 [ERROR] 
98112 [ERROR] For more information about the errors and possible solutions, please read the following articles:
98113 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
The command '/bin/sh -c mvn --batch-mode -Dmaven.test.skip=true clean package' returned a non-zero code: 1

[stefanocudini]

I suppose that this bug causes error to compiling .war in all old versions published in dockerhub

[Botnary]

Same error here, any ideas or work around to this issues?

[Wojdom]

What I did was to download missing dependencies and manually install them in my local maven repository. It helps, however using remote repository would be much easier.

[stefanocudini]

Same error here, any ideas or work around to this issues?

the problem I suppose is http(not ssl) artifactory repos

[koen-dejonghe]

I didn't even know it was compiling inside the docker container. Why isn't the war file deployed as such? I worked around this by using a running container with an already compiled war file, committed it, and made a new image out of it. Anyway this compiling inside the docker container makes it very brittle as shown by this problem, and defeats the purpose of Docker somehow.