Closed meowcat closed 3 years ago
Its probably a firewall issue. Pls try to open http://gose.fiehnlab.ucdavis.edu:55000/content/groups/public/edu/ucdavis/fiehnlab/fiehnlab-pom/1.0.11-SNAPSHOT/maven-metadata.xml manually. If it does not work your firewall is blocking host gose.fiehnlab.ucdavis.edu at port 55000
This worked:
wget http://gose.fiehnlab.ucdavis.edu:55000/content/groups/public/edu/ucdavis/fiehnlab/fiehnlab-pom/1.0.11-SNAPSHOT/maven-metadata.xml
--2021-04-15 11:59:09-- http://gose.fiehnlab.ucdavis.edu:55000/content/groups/public/edu/ucdavis/fiehnlab/fiehnlab-pom/1.0.11-SNAPSHOT/maven-metadata.xml
Resolving gose.fiehnlab.ucdavis.edu (gose.fiehnlab.ucdavis.edu)... 128.120.143.183
Connecting to gose.fiehnlab.ucdavis.edu (gose.fiehnlab.ucdavis.edu)|128.120.143.183|:55000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 824 [application/xml]
Saving to: ‘maven-metadata.xml’
maven-metadata.xml 100%[============================================================================>] 824 --.-KB/s in 0s
2021-04-15 11:59:10 (115 MB/s) - ‘maven-metadata.xml’ saved [824/824]
Besides, the script has always worked on this machine until at least two weeks ago...
Checking the Maven docker image, it would appear that they switched to Maven 3.8.1 11 days ago. https://github.com/docker-library/official-images/commit/94c9a2a17d5a08114504b305059a6c4af54e1cbd#diff-79f56c4595d485f2c306310171f04dcd7d027f418e1a6bee7186dedd2fbedb7c
3.8.1 introduces a change in behaviour where external HTTP insecure URLs are now blocked by default: https://maven.apache.org/docs/3.8.1/release-notes.html#why-does-this-version-have-the-value-3-8-1
Ok, I was too lazy to actually try this. I have tried it and can reproduce it. Your hints will help me fixing this. I will report back.
Quick fix is using maven:3.6-jdk-11
in compose (waiting for it to build, but seems to work.) The "defining mirror" thing I don't really understand.
Your quick fix is working for me. Thanks! I pushed the changes to the dev branch. Do you need a backport to the resent release? If its not very urgent, it will be in the next release.
The "defining mirror" is nothing we can apply at the repo. Its a personal setting for every user and that's why not well suited as a permanent fix.
I also moved the problem to some one else desk... https://github.com/berlinguyinca/spectra-hash/issues/48
Thanks for reporting and solving. I will close for now. Feel free to reopen if you need the stable release with the fix.
The "defining mirror" is nothing we can apply at the repo. Its a personal setting for every user and that's why not well suited as a permanent fix.
OK, I suspected that.
Your quick fix is working for me. Thanks! I pushed the changes to the dev branch. Do you need a backport to the resent release? If its not very urgent, it will be in the next release.
Thanks! No backport needed, I use dev anyway.
Also found in relation to this: https://stackoverflow.com/questions/66980047/maven-build-failure-dependencyresolutionexception