jfrog artifactory could not validate router error
Alexey, I suspect ipv6 ip being picked up by the start-script, causing this. Can you update your system.yaml (will be in var/etc/ folder) with the following and try? shared: node: ip: <your ipv4 IP>
Alexey, I suspect ipv6 ip being picked up by the start-script, causing this. Can you update your system.yaml (will be in var/etc/ folder) with the following and try? shared: node: ip: <your ipv4 IP>
I’m sure that if you only talk about storing binaries from “mvn deploy” both will do fine. We use Artifactory very extensively with all upgrades along the way. Lots of projects, numerous snapshots deployed and external repos proxied. Not a single problem. I find it hard to explain how other people experience issues with its … Read more
You need to add an ivysettings.xml file with the following repositories listed (resolvers in ivy speak) <ivysettings> <settings defaultResolver=”chain”/> <resolvers> <chain name=”chain”> <ibiblio name=”central” m2compatible=”true”/> <ibiblio name=”example” m2compatible=”true” root=”http://example.com/m2/”/> </chain> </resolvers> </ivysettings> In my opinion it makes more sense to separate the dependency declaration (ivy.xml) from the mechanism of retrieval (settings.xml). This is not needed … Read more
I used to solve this issue by deleting the corresponding failed to download artifact directory in my local repo. Next time I run the maven command the artifact download is triggered again. Therefore I’d say it’s a client side setting. Nexus side (server repo side), this issue is solved configuring a scheduled task. Client side, … Read more