Extend workflow to upload built JAR as a CI artifact #9
Conversation
This file contains 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
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Discussed as part of today's call re the testing of #8, this PR proposes a simple modification to the GitHub workflow to upload the JAR built under
targetas an artifact.While I was enabling this, I realized that the current POM packages everything as a 65 MB uber JAR. I assume this is not strictly necessary but rather a convenience. In the same spirit as #8 (comment), can we think of a simpler scenario where only this component would be packaged and could be simply dropped into either the command-line tools and/or the ImageJ/Fiji distribution?