Instead of relying on the BuildTools-only spigot artifact, we now rely on the publicly available spigot-api artifact. This is possible, since the API does not make use of any CraftBukkit or NMS code or any other code that is exclusively provided by the spigot artifact. The scope is also set to provided, so the artifact isn't needlessly shaded into the final jar. This change will help developers who want to make use of this API by ensuring the artifact can be fetched online, without having the run BuildTools first. Compatibility is still ensured, since the minimum version is still at 1.9.
This differs from pull request #6 since it doesn't require you to drop versions 1.9-1.11. That being said only this pull request or pull request #6 should be merged. The other one should be closed, since the main issue (Apache Maven being unable to find the non-existent local artifact) will be fixed by merging either pull request.
Maximvdw
commented
5 years ago
Instead of relying on the BuildTools-only spigot artifact, we now rely on the publicly available spigot-api artifact. This is possible, since the API does not make use of any CraftBukkit or NMS code or any other code that is exclusively provided by the spigot artifact. The scope is also set to provided, so the artifact isn't needlessly shaded into the final jar. This change will help developers who want to make use of this API by ensuring the artifact can be fetched online, without having the run BuildTools first. Compatibility is still ensured, since the minimum version is still at 1.9.
This differs from pull request #6 since it doesn't require you to drop versions 1.9-1.11. That being said only this pull request or pull request #6 should be merged. The other one should be closed, since the main issue (Apache Maven being unable to find the non-existent local artifact) will be fixed by merging either pull request.