Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the pull
Allows plugins to use Maven to pull in the lambda api jar instead of copy pasting jar's around like cavemen.
This only publishes to local maven which will be picked up by jitpack builds, this is what i'd recommended for ease of use in lieu of lambda's own maven repo.
Describe how this pull is helpful
Allow for easier updating of api jars for plugin devs. Also removes the jars as an attack vector for rogue plugin devs.
Additional context
What this would look like in a plugin's build.gradle:
This of course is linked to my own repo and commit hash for example's sake.
It can be linked to the main lambda repo and a named official release after this is merged.
You can view the various versions jitpack creates by browsing here for example: https://jitpack.io/#rfresh2/lambda/