Maven coordinates metadata for projects and versions #107
BasiqueEvangelist
started this conversation in
Feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Right now, if you want to see a project's maven coordinates, you can read the description (if the author put them there, that is), or search for them on GitHub. This is fine for library mods, which are, well, made to be depended on. It does mean that it's a bit harder to find where a non-library mod is hosted, though, as authors aren't keen on specifying coordinates. This can sometimes lead to having to search for the proper maven coordinates in other people's
build.gradle
.Of course, if there is no proper maven repo for the project, Modrinth Maven can always be used. There are some problems with it, however:
This leads to janky buildscripts, as all transitive dependencies have to be specified. Of course, this is most likely the modder's fault, but an easier way to show exactly what you need to depend on would be nice.
While the coordinates are supposed to be easy to specify, with minimal meaningless IDs, they can become rather painful once you have duplicate version numbers. Some people have already asked for help with this. It would be rather nice for the correct coordinates to be shown on the website, especially if modrinth/labrinth#624 is implemented.
Proposed solution
The backend will supply the recommended (the author's repo or modrinth maven) maven coordinates and repo with the version's data. If the project/version doesn't have any maven coordinates, the backend will send the modrinth maven coordinates instead.
Example:
The frontend can then use this information to show the version's coordinates and example code for depending on this version in the version page, possibly with a disclaimer if the version has no blessed repo.
Beta Was this translation helpful? Give feedback.
All reactions