It seems that the jar is missing.
~ => wget http://central.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
--2017-11-27 11:22:29-- http://central.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
Resolving central.maven.org... 151.101.40.209
Connecting to central.maven.org|151.101.40.209|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-11-27 11:22:29 ERROR 404: Not Found.
It seems that jms 1.1 has been removed from maven central long time ago because of licensing issues, look here
Related
I'm struggling with a simple test using JFrog Artifactory Cloud when creating a remote repository to adobe public one.
I configure a remote as maven repository, on URL I've inserted https://repo.adobe.com/nexus/content/repositories/public and test ok on name just give a adobe-public name and click on save and finish.
After that I'm trying to obtain a existing (in repo.adobe.com) pom from https://xxxx/artifactory/adobe-public/com/day/jcr/vault/... but I can't get any pom.
I've tried to change several cache settings or offline settings but issue is always ""message" : "adobe-public: is offline". status 404.
On Logs, https://cccc/ui/admin/artifactory/advanced/system_logs there isn't also anything useful.
Thank you in advanced.
This is caused by global offline mode being active.
I had same issue.
Solved in: "https://.../ui/admin/artifactory/configuration/artifactory_general" - turn off "Global Offline Mode" and save.
Have a similar setup with Maven repository pointing to https://repo.adobe.com/nexus/content/repositories/public and was successfully able to download the pom files, refer the below snippet,
$ wget --user=admin --password=Password https://myartifactory/artifactory/adobe-repo/ant/ant/1.5.1/ant-1.5.1.pom
--2020-11-01 10:27:54-- https://myartifactory/artifactory/adobe-repo/ant/ant/1.5.1/ant-1.5.1.pom
Resolving myartifactory (myartifactory)... 1.2.3.4, 2.1.3.5, 3.7.7.4
Connecting to myartifactory (myartifactory)|1.2.3.6|:443... connected.
HTTP request sent, awaiting response... 401 Unauthorized
Authentication selected: Basic realm="Artifactory Realm"
Reusing existing connection to myartifactory:443.
HTTP request sent, awaiting response... 200 OK
Length: 140 [application/x-maven-pom+xml]
Saving to: ‘ant-1.5.1.pom’
ant-1.5.1.pom 100%[====================================>] 140 --.-KB/s in 0s
2020-11-01 10:27:59 (5.14 MB/s) - ‘ant-1.5.1.pom’ saved [140/140]
Use wget and try to download the file as I did. Also, the error "offline" says that the repository is offline and cannot be downloaded, goto to the repository's configuration page under Artifactory UI --> Admin --> Repositories | Adobe-public and under the Basic tab, scroll down and look for "offline", if this "offline" is checked, uncheck it and try again.
I'm using wget to retrieve the Instagram JSON from the URL https://www.instagram.com/instagram/?__a=1.
Running wget from my local Manjaro setup returns a 200 OK and the proper JSON response, but running it from a Debian server retrieves a 302 found.
At first I thought it could be because of the wget version differences, but running curl locally also works while wget doesn't work properly.
Is there anything that I should be setting up on my server to get a proper response? My guess is that the HTTPS connection is refusing my server from connecting properly.
So, this is a weird quirk of the Instagram servers. Nothing you can do about it.
The problem is that Instagram responds differently depending on whether you connect to their server over IPv4 or IPv6. Why they would do that is beyond me, but I can reliably reproduce the result by controlling for only this variable.
IPv4:
$ wget -O/dev/null -4 "https://www.instagram.com/instagram/?__a=1"
--2020-09-03 14:22:15-- https://www.instagram.com/instagram/?__a=1
Resolving www.instagram.com (www.instagram.com)... 157.240.27.174
Connecting to www.instagram.com (www.instagram.com)|157.240.27.174|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 118552 (116K) [application/json]
Saving to: ‘/dev/null’
100%[================================================================================================================================>] 118,552 306KB/s in 0.4s
2020-09-03 14:22:17 (306 KB/s) - ‘/dev/null’ saved [118552/118552]
IPv6:
$ wget -O/dev/null -6 "https://www.instagram.com/instagram/?__a=1"
--2020-09-03 14:22:54-- https://www.instagram.com/instagram/?__a=1
Resolving www.instagram.com (www.instagram.com)... 2a03:2880:f23f:e5:face:b00c:0:4420
Connecting to www.instagram.com (www.instagram.com)|2a03:2880:f23f:e5:face:b00c:0:4420|:443... connected.
HTTP request sent, awaiting response... 302 Found
Cookie coming from www.instagram.com attempted to set domain to www.instagram.com
Cookie coming from www.instagram.com attempted to set domain to www.instagram.com
Location: https://www.instagram.com/accounts/login/?next=/instagram/%3F__a%3D1 [following]
--2020-09-03 14:22:54-- https://www.instagram.com/accounts/login/?next=/instagram/%3F__a%3D1
Reusing existing connection to [www.instagram.com]:443.
HTTP request sent, awaiting response... 200 OK
Cookie coming from www.instagram.com attempted to set domain to www.instagram.com
Cookie coming from www.instagram.com attempted to set domain to www.instagram.com
Length: 48094 (47K) [text/html]
Saving to: ‘/dev/null’
100%[================================================================================================================================>] 48,094 --.-K/s in 0.04s
2020-09-03 14:22:54 (1.28 MB/s) - ‘/dev/null’ saved [48094/48094]
This is the same thing you see in your debug logs. On Manjaro, it makes a IPv4 connection, while on Debian it makes a IPv6 connection leading to the differences.
Welcome to the world of crazy webservers :)
In any case, the answer to your question then is to use only a IPv4 connection
When I run my maven build pointing to the JFrog Artifactory setup I see the following error in the log:
2020-05-14T04:41:01.640Z [jfrt ] [ERROR] [dcb2a29d3c46472e] [o.a.r.RemoteRepoBase:806 ] [http-
nio-8081-exec-1] - IO error while trying to download resource
'jcenter:org/springframework/security/spring-security-web/4.2.2.RELEASE/spring-security-web-
4.2.2.RELEASE.jar': **javax.net.ssl.SSLException: Connection reset**
2020-05-14T04:41:01.641Z [jfrt ] [WARN ] [dcb2a29d3c46472e] [o.a.e.DownloadServiceImpl:266 ] [http-
nio-8081-exec-1] - **Sending HTTP error code 404: Connection reset**
I have checked the connectivity to the jcenter repo from within the Artifactory admin conosole, and its says that its able to connect.
Require your assistance.
Regards
Please check the URL you are using for JCenter and make sure it is using secure HTTP - https://jcenter.bintray.com.
Starting in January 2020, JCenter is only serving requests made with HTTPS. From that point on, all requests made with HTTP are denied and any builds that use a JCenter URL with the non-secure HTTP protocol will fail.
For more info see the following blog post.
I am trying to bitbake linux-imx with following command in my source recipe:-
KERNEL_SRC ?= "https://username:passsord#vcs.rafi.cloud/scm/f-pep2219002-akka/evalkit-powerecu-2.git;protocol=https"
I am receivin the following error:-
Resolving vcs.rafi.cloud (vcs.rafi.cloud)... 192.81.121.25 Connecting
to vcs.rafi.cloud (vcs.rafi.cloud)|192.81.121.25|:443... connected.
HTTP request sent, awaiting response... 501 2019-09-16 13:05:48 ERROR
501: (no description)
What is the reason for this error and how to resolve it ?
I've not tested this but based on a quick look at the code I believe this might work:
git://vcs.rafi.cloud/scm/f-pep2219002-akka/evalkit-powerecu-2.git;protocol=https;user=username:password
I'm using conda to download a pkg, but failed with "CondaHTTPError: HTTP 404 NOT FOUND for url https://mirrors.ustc.edu.cn/anaconda/cloud/bioconda/noarch/repodata.json". Hope the public mirrors in china could be supported soon.