Open Galster-dev opened 1 year ago
Could we just filter out pom dependencies completely?
Some pom dependencies are meta packages containing a few jar artifacts
How would you expect to handle these on the PluginLoader side? Does it provide the necessary functionality to parse & handle metadata packages?
Yes, DefaultArtifact
has both constructors with classifiers/extension and can parse it from a single so called "coords" string (format available here)
Exported dependency coords do not include classifiers and extensions. This leads to some bugs, e.g. server trying to download
jar
artifact forpom
dependency (withPluginLoader
implementation presented in README)My personal workaround atm is exporting artifacts instead of dependencies, but you may not like it because of increased JSON file size.