Skip to content

Delete apps-contrib/resources/kinetic-merge.json - #353

Open
sageserpent-open wants to merge 1 commit into
coursier:mainfrom
sageserpent-open:patch-1
Open

sageserpent-open wants to merge 1 commit into
coursier:mainfrom
sageserpent-open:patch-1

Conversation

@sageserpent-open

@sageserpent-open sageserpent-open commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Kinetic Merge has been split into a core library plus two CLI applications that use the core, so it no longer makes sense to point Coursier at what is now purely a library artifact.

I trust that a straight file deletion is OK for this, but if it makes more sense to keep the entry for Kinetic Merge with a pinned version number for the last all-in-one release, then let me know and I’ll do that instead.

@sageserpent-open

Copy link
Copy Markdown
Contributor Author

I should mention that it was I who raised #265 that introduced the entry for Kinetic Merge. 😄

@sageserpent-open

Copy link
Copy Markdown
Contributor Author

… but if it makes more sense to keep the entry for Kinetic Merge with a pinned version number for the last all-in-one release, then let me know and I’ll do that instead.

Given the build error, looks like that’s the only option. I’ll rework this PR…

…his was the final release prior to the applications being hived off from the publihsed library.
@sageserpent-open

Copy link
Copy Markdown
Contributor Author

OK, I've force pushed ce9cc37 so as to merely curtail the revisions of Kinetic Merge that can be distributed, but this still fails the validation step, as there are subsequent library-only releases published to Sonatype. Ironically, that's why this PR exists in the first place. 😁

I'm hoping that while validation fails due to this technicality, the other two builds steps succeed, so can this be merged anyway without breaking Coursier?

@tgodzik

tgodzik commented Oct 19, 2026

Copy link
Copy Markdown
Collaborator

curious, we should be able to just remove it. @alexarchambault did some changes on it recently, so maybe the validation is too strict?

Alternatively, you can override the jar used for newer versions of the library (use instead one of the jars that it was split into)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants