Prefix Maven artifacts with kable-
#692
Merged
Conversation
This file contains 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
twyatt
added
the
maintenance
cedrickcooke
approved these changes
Jun 12, 2024
sdonn3
approved these changes
Jun 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We've seen issues for library consumers that manifest in various ways when multiple libraries have the same Maven artifact name.
Most recently, with the K2 upgrade, on the consumer side, we saw failures similar to:
This occurred because our internal project had an
encodingmodule which clashed with Tuulbox's and another of our internal libraries artifacts namedencoding.We resolved it by renaming our internal library's Maven artifact to be prefixed.
Additionally, it seems to be standard for libraries to prefix their Maven artifact names, for example: kotlinx-coroutines-core