Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Gradle dependency resolution with Proget
-
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
.mavenProget storage directory and it shows up there with the correct contents.
-
Although ProGet can handle invalid version numbers for Maven packages, this one is a extra invalid version number (it starts with a "v") and unfortunately we can't support them at this time.
ProGet requires that packages follow the ~20 year Maven standard that "packages start with a letter and versions start with a number". Sadly this team didn't like those standards and opted to do their own thing.
The issue comes with identifying whether
com/google/apis/google-api-services-healthcare/v1-rev20240731-2.0.0is an artifact or a version. Because ProGet is not a basic file server, things like package names and versions matter.Anyway this will require a significant and risky change to the API so we won't consider it at least for another major release.
-- Dean
