Record why the artifactId is geojson, not geojson-layer - #9
Merged
Conversation
The repository, the Gradle module and the npm package are all named `geojson-layer`, but Maven Central has carried this module as `com.mapconductor:geojson` since 1.0.0. Central cannot rename or delete a published coordinate, so aligning the name would mean publishing a second artifact and asking every consumer to migrate. The mismatch stays. Say so next to the declaration, otherwise someone will eventually 'fix' it — during the 1.3.1 release the publish workflow already carried `geojson-layer`, which made its Maven Central metadata lookup 404 and silently disabled the already-published check.
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.
The repository, the Gradle module and the npm package are all named
geojson-layer, but Maven Central has carried this module ascom.mapconductor:geojsonsince 1.0.0.Central cannot rename or delete a published coordinate, so aligning the name
would mean publishing a second artifact and asking every consumer to migrate.
The mismatch stays. Say so next to the declaration, otherwise someone will
eventually 'fix' it — during the 1.3.1 release the publish workflow already
carried
geojson-layer, which made its Maven Central metadata lookup 404 andsilently disabled the already-published check.