Hi @stevedennis ,

I started with a maven feed with two unfiltered connectors to remote repos:
First connector: https://repo1.maven.org/maven2/
Second connector: https://build.shibboleth.net/maven/releases/

Running the command
curl -I https://my.server.com/maven2/myfeed/org/opensaml/opensaml-security-api/4.1.1/opensaml-security-api-4.1.1.pom
should return 200 and then right after that run
curl -I https://my.server.com/maven2/myfeed/org/opensaml/opensaml-security-api/4.1.1/opensaml-security-api-4.1.1.jar
which returns a 404.

Now remove the maven connector and clearing cache leaving us with just shibboleth:

Now run both the commands above again which should return 200 for both.

Hi,

I was having some trouble with pom files being retrieved but not my jar files when building my gradle project. I think I pinpointed the issue with the connectors.

For some context, I have a maven feed with multiple connectors. One of the connectors being the maven connector. Other connectors are from remote maven repos and self-connectors.

Back to the issue, I have tested building my gradle project with just one connector which is the maven central connector (https://repo1.maven.org/maven2). That worked fine up until it needed other dependencies from other remote repos (i.e. https://build.shibboleth.net/maven/releases/). I added another connector and then that's when the issue of the jar missing but the pom file retrieved problem comes back.

One of the dependency it's trying to retrieve is org.opensaml:opensaml-security-api:4.1.1. Both maven central and shibboleth have those coordinates. I have read in the docs about connector filters but there is a lack of info on the filter format or examples for maven connectors. I was thinking of blocking the package from the maven central connector so that only the shibboleth connector is used to retrieve the artifacts. I have the following filters set in the maven central connector:

How would I go about this issue? Did I format or use wildcard properly for maven feeds? Am I going about this all wrong?

Thank you!

Web UI Version: 2024.38 (Build 1)
Database Schema Version: 24.0.38.1

Hi @stevedennis

After a couple weeks of some testing, I've come to the conclusion that whenever I have the Connector Package Caching enabled on the feed level I run into the issue mentioned above.

Disabling the caching built my project successfully but I still want to have caching enabled. Is there a reason why this could be happening?

Whenever I try to build my project with gradle I get an error saying that it could not parse the POM file. The artifact in specific is com.google.apis:google-api-services-healthcare, which is from a maven central connector for my feed.

Proget manages to see all the versions but when I click on a pom file it takes me to a empty maven2 page like:

If I pull the artifact using the web ui it manages to pull the pom but clicking on it redirects me to an empty directory like the image above.

I have checked if the pom file exists in the local .maven Proget storage directory and it shows up there with the correct contents.

@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.