Add reference jars for publishing to maven-central#305
Open
mgaffigan wants to merge 1 commit into
Open
Conversation
Signed-off-by: Mitch Gaffigan <mitch.gaffigan@comcast.net>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds server/setup/refs containing "abi-only" jars that can be used for plugin build.
Tested against:
If I'm missing some, let me know where to find the plugin jars and we can re-generate the "public" api lists with jdeps. See https://github.com/mgaffigan/oie/tree/mirthlibscan for the script used to generate the refs files.
Long term, this should be replaced by proper layered build, but that's expensive and maven is high value, so merging as interim is still valuable.