practicalli / practicalli/clojure
Publishing uberjars to AWS S3 buckets
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 117
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Maven command or Clojure lib someone made that uploads a jar file to a S3 bucket?
aws s3 cp uberjar md5sums
https://github.com/kennyjwilli/s3-mvn-upload - uploads a jar file to Aws S3
Without md5sums or similar checksum file, you wiil receive this message from tools-deps
"Download corrupted: Checksum validation failed, no checksums available."
The jar will works (i.e., jvm starts up with the jar on the cp) but better to add the checksum files
the correct way is to compute an md5 or sha1 checksum for the jar and upload those (and ideally to gpg sign all of those files as well).
I do not know of a tool that does that (although I have started working on one)
an example of what goes into maven central is something like this: https://repo1.maven.org/maven2/org/clojure/tools.deps.alpha/0.8.677/
how that all gets created and uploaded is quite complicated, and clojars does much less (and even less is really required)
really, just the jar and the md5 or sha1 file (and ideally the pom) are probably sufficient
you can use a tool like sha1sum or md5sum to make that
there is also a version metadata file that should be updated too (like https://repo1.maven.org/maven2/org/clojure/tools.deps.alpha/maven-metadata.xml) if you want something like RELEASE version to work.
I would like to handle a) clojars b) s3 and c) maven central in that order which I think handles both the most common and easiest items first
there are multiple options on each and it is way harder than it should be for sure
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced s3-mvn-upload project and the tools-deps checksum failure, then compare the artifact files and metadata shown in the Maven Central example. Done would require a defined approach for publishing to Clojars, S3, and Maven Central, including checksums and the requested metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, clojure
- Domain
- cloud, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100