Summary
When using the latest development builds (for my uses, the builds from Jan 5 for the interact event) in my maven dependencies, the actual downloaded repositories in my .m2 folder do not contain the correct version naming under the Mythic-Plugin repository. For example, if I use the Mythic-Dist artifact id in my dependency, it will download Mythic-Dist but also try to download Mythic-Plugin, which fails as instead of replacing the ${mythicversion} tag with the actual version in the Mythic repository, it will keep it and thus maven will not be able to find the actual repo in the nexus repository. [Legacy attachment omitted]
Steps to reproduce
Add the latest dev build as a dependency in maven, it should fail to download.
Current behavior
Same as in summary.
Intended correct behavior
Instead of the ${mythicversion} tag being listed in the file paths, it should be replaced with whatever dev build is being downloaded (like 5.0.0-...).
Server log file
N/A
Debug log snippet
N/A
Proposed fixes
Not sure here... I've looked through the pom files in each 5.0.0 repo, and I don't see any apparent issues (then again, not super familiar with multi-modular projects)