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 target as 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 https://github.com/ome/ZarrReader/pull/8#issuecomment-932234869, 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?
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
target
as 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 https://github.com/ome/ZarrReader/pull/8#issuecomment-932234869, 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?