massive-com / massive-com/client-jvm
Not having this on Maven Central is such a bad developer UX
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 38
- Avg merge
- 32m
- Merged PRs (30d)
- 2
Description
Really it makes me want to go over to databento... Is there any way to use this? I tried the jitpack thing and it just does not work, at least it doesn't show up on my classpath
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Start by locating the repository's dependency-publication and release configuration, then determine whether a Maven Central artifact is intended. Done means the published client can be resolved on the JVM without relying on a failing JitPack setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100