@Dan_Woolf I have the 2024.38 version of Proget

@atripp So I have been testing other dependencies and it's giving the same result. For example, I'm trying to pull this dependency

I noticed that it only downloads the .pom file. The other artifacts show up but when I click on the .jar it still says File not found on disk. The weird thing is when I delete the .pom artifact only then I can click on the .jar since it can be found now.

I have tried clearing cache and also re-indexing but it always does this. This only happens when I use connectors. Whether it be a remote repo connector or a connector a proget feed. I also made sure the global settings allow invalid version/non standard files to be deployed to the feed. I also set the block settings to allow download for noncompliant packages.

Is there anything else I can try to resolve this?

I'm trying to use my maven feed on ProGet on gradle for dependency resolution. My feed has connectors for remote repos such has maven central, gradle plugins, etc.

My problem now is that whenever I'm building my project I get the error for a couple dependencies but this is one example

Could not find hamcrest-core-1.3.jar (org.hamcrest:hamcrest-core:1.3).
     Searched in the following locations:
         http://my.server.local:8624/maven2/my-feed/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar

When I check the feed it has the artifacts but when I click on the jar files it gives me a page.

This doesn't make sense since I'm using the maven central repo. Would I need to download each artifact manually from the maven central repo?

I feel like I'm missing something or fetching the feed wrong.

When I am creating a new maven2 feed and add artifacts from Artifactory I get an error shown below:

Unhandled exception: System.Net.WebException: The remote server returned an error: (404) .

I did some digging and I pinpointed the main issue which was that the repository I was importing from did not have ./index/nexus-maven-repository-index.gz.

My question now, is it possible to bypass that error? It's not only that repository but I also want to create connectors to remote repositories but some of the endpoint urls also don't have that repository index.