Skip to content

[Plugins] Parse maven-metadata.xml when downloading #1049

@topi314

Description

@topi314

Change request

Right now Lavalink expects the maven artifacts to have the exact name as the artifact id.
But this isn't always the case, as an example when publishing a -SNAPSHOT release maven replaces SNAPSHOT with the current date. This then causes Lavalink to not being able to download the plugin anymore.

The solution is to instead read in the maven-metadata.xml which then points to the correct artifact for a certain plugin. What this also means is that you need a propper maven repository with a maven-metadata.xml to host Lavalink plugins, which was previously not needed.

Ideally we would implement this as an addition to the current way of doing it, which would allow us to not have to do this anymore.

Relevance

yes

Could this be a plugin instead?

no

Checklist

  • I have checked for duplicate issues
  • I have checked for existing plugins

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions