Hello. Sporadically, it happens that my builds fail due to the fact that certain dependencies cannot be fetched from the Maven central repo, due to connection timeouts.
This is a double problem:
* first, these dependencies were already fetched by previous builds, but I could not figure out yet how to have the local maven repo to be reused (I tried all the three possibilities in the Maven build step with no effect, I also opened a topic on the forum with no answer)
* these dependencies are indeed present in the central repo (in this example, we are talking about commons-cli:commons-cli:jar:1.4).
02:32:35 [ERROR] Failed to execute goal on project base-vaadin: Could not resolve dependencies for project com.anteash:blah-blah-blah:jar:1.33.2-SNAPSHOT: Could not transfer artifact commons-cli:commons-cli:jar:1.4 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/commons-cli/commons-cli/1.4/commons-cli-1.4.jar: Connect to repo.maven.apache.org:443 [repo.maven.apache.org/18.104.22.168] failed: Connection timed out (Connection timed out) -> [Help 1]
02:32:35 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
02:32:35 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
02:32:35 [ERROR] For more information about the errors and possible solutions, please read the following articles:
02:32:35 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
02:32:35 [ERROR] After correcting the problems, you can resume the build with the command
02:32:35 [ERROR] mvn <args> -rf :blah-blah-blah
02:32:35 Process exited with code 1