I’m trying to go from version 2.0 to version 2.0.public_draft of javax.servlet: jsp-api. locally it is done without problem but online Travis CI has trouble downloading the dependencies from the central repository: this is the error :
Failed to execute goal on project openmrs-web: Could not resolve dependencies for project org.openmrs.web:openmrs-web:jar:2.4.0-SNAPSHOT: Failure to find javax.servlet:jstl:jar:1.2.0 in https://maven-central.storage-download.googleapis.com/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of google-maven-central has elapsed or updates are forced -> [Help 1]
in my research they suggest me much more to reconfigure the URL repository
please someone could have an idea how to solve this problem.
thanks cc: @mozzy , @sharif , @herbert24 , @dev1
Kindly share the entire error log using paste bin for easy identification of the would be problem alternatively share the link to your commit.
Okay! I once did this ticket and dropped it but I believe you can make it. When you click on the Travis-ci/PR details on your PR, you will access the error log which I believe looks like this https://pastebin.com/c4MAYF6w causing the error on the openmrs- web failure.
Have you tried the suggested solutions on this link https://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException?
According to the upgrade you made, Try removing version 2.0.public_draft, before that change travis was passing
Kindly forgive me ! I have been asking myself the essence of shifting from
version 2.0 to version 2.0.public_draft of javax.servlet: jsp-api which I haven’t got answer and I believe you can help me understand.
@sharif 2.0.public_draft is among the ticket description . and it is because of the version 2.0.public_draft that Travis is failing.
Thanks @jwnasambu for bringing this up
That seems like a regression. 2.0.public_draft sounds like a beta/alpha and 2.0 is the complete release. you can drop the upgrade and go for another library
Thanks my mentor for the clarification. @achilep as you upgrade a library kindly confirm that the dependencies are also upgraded that is if they exist in the pom.xml.
thank you @mozzy , @jwnasambu and @sharif for orientattion