Multi Connector Feed

[misael.esperanzate_5668]

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

[stevedennis]

Hi @misael-esperanzate_5668 ,

When one of the connectors reports a 404, ProGet should move on to the next connector to search. Can you help set up a reproduction case using the ProGet UI and URLS (perhaps some basic curl commands)? You should be able to do everything with basic GET requests, and see different results.

That'll make it a lot easier to test and see if we can reproduce the issue.

Thanks,
Steve

[misael.esperanzate_5668]

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.

[atripp]

@misael-esperanzate_5668 thanks for the reproduction details!

I was ablet to reproduce this very easily and fixed it via PG-3091 - it was an ordering problem

This will be in the upcoming maintenance release this Friday