Fix CLI module to publish unclassified fat JAR as primary artifact#995
Closed
Fix CLI module to publish unclassified fat JAR as primary artifact#995
Conversation
|
Formatting check succeeded! |
|
brynrhodes
approved these changes
Apr 7, 2026
Contributor
|
Tested locally, doesn't quite produce the same artifact layouts. Reused the idea in #996 |
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
3 participants
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.
Since the Spring Boot Gradle plugin was applied to cqf-fhir-cr-cli, the standard jar task was disabled by default and only classified JARs (-plain, -javadoc, -module) were published to Maven Central. Downstream projects depending on cqf-fhir-cr-cli:jar (without a classifier) got 404s from Maven Central, breaking builds that unpack the CLI fat JAR.