README.md: say how to take it into a project - #4
Merged
Conversation
The README documented the pinned JDK and the Makefile — how to develop the library — and never said how to consume it. A Getting it section now states that it ships as source, that the implementation is ready and the package is not yet published, and gives both source paths as exact lines. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Docs only. Part of a family-wide pass making every distribution claim honest against the registries.
The claims found. None — and that is the gap. The README's only distribution-adjacent line is "A plain Makefile drives everything — no Maven, no Gradle", under Toolchain, which is about developing this repo. There is no install line, no coordinate, no statement of what the library is distributed as, and nothing telling a reader how to get
import serialize.*;(USAGE.md line 11) to compile in their own project.The registry fact. Nothing on Maven Central. The Maven Central search for
a:serializereturns three artifacts, all other people's (org.mvnpm.at.keyv,org.mvnpm.at.emotion,io.github.magicpluginteam); no group under mas-bandwidth exists. There is nopom.xmlor Gradle file in the repo, so no coordinate has been chosen either.Changed. A new
## Getting itsection ahead of The surface: it ships as source today, the implementation is ready and the package is not yet published, there is no artifact on Maven Central under any coordinate and no Maven or Gradle build here to produce one, and publishing is a separate round. Then the two source paths, exact:src/serialize/(15 files, zero dependencies) into your own source tree;javac --release 17 -d classes serialize.java/src/serialize/*.javathenjar cf serialize.jar -C classes serialize— and compile against-cp serialize.jar.Plus the
-ea/ no--eanote that matches the two shapes the suite tests, and pin a tag, v1.1.0 current.No version bumps, no code changes.
🤖 Generated with Claude Code