maven - gradle fails to resolve dependency via nexus proxy repository -


i'm new nexus (and maven matter). i'm in process of migrating existing nexus config new server , having little issue. serving local artifacts fine, when gradle tries resolve particular dependency fails locate artifact. resolves fine against old repository. both old , new repositories configured proxys

> not resolve org.jboss.ws.native:jbossws-native-jaxrpc:3.0.4.ga.   required by:       xxx.xxx:0.0.1-snapshot > org.jboss.ejb3:jboss-ejb3-ext-api:1.0.0 > org.jboss.javaee:jboss-ejb-api:3.0.0.ga > not find version matches org.jboss.ws.native:jbossws-native:3.0.4.ga. 

now, confusing bit.

the new repo proxy , uses exact settings old 1 uses. can browse new repo in nexus , see offending artifact. can search artifact name is found fine. difference can see between 2 old repo has cache of remote artifacts , new 1 has yet cache anything

here relevant config (same on both)

type: proxy provider: maven2 format: maven policy: release default local storage: file:///home/nexus/sonatype-work/nexus/storage/jboss remote storage location: https://repository.jboss.org/ download remote indexes: true auto blocking enabled: false file content validation: true checksum policy: warn (no auth set up) not found cache ttl: 1440 artifact max age: -1 metadata max age: 1440 item max age: 1440 

any tips awesome, i'm going little mad


Comments

Popular posts from this blog

amazon web services - S3 Pre-signed POST validate file type? -

c# - Check Keyboard Input Winforms -