Skip to content

Support use of snakeyaml-engine on java 8+ and legacy snakeyaml on Java 7#585

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 4 commits intomasterfrom
mcculls/use-snakeyaml-engine-on-java8
Apr 10, 2026
Merged

Support use of snakeyaml-engine on java 8+ and legacy snakeyaml on Java 7#585
gh-worker-dd-mergequeue-cf854d[bot] merged 4 commits intomasterfrom
mcculls/use-snakeyaml-engine-on-java8

Conversation

@mcculls
Copy link
Copy Markdown
Contributor

@mcculls mcculls commented Feb 11, 2026

Note the default "jar-with-dependencies" artifact still only contains the legacy snakeyaml library, to avoid any increase in its size. If we wanted to include both snakeyaml and snakeyaml-engine libraries then "jar-with-dependencies" would increase by ~290Kb

At runtime the appropriate YAML parser is loaded based on the Java version and which library is available on the runtime class-path.

This means downstream consumers that only use Java 8+ can decide to include the snakeyaml-engine library when embedding JMXFetch and skip the legacy snakeyaml library.

@mcculls mcculls force-pushed the mcculls/use-snakeyaml-engine-on-java8 branch from 1249d98 to bddeb5d Compare February 11, 2026 21:51
@mcculls mcculls force-pushed the mcculls/use-snakeyaml-engine-on-java8 branch from bddeb5d to 631025a Compare February 12, 2026 12:01
@mcculls mcculls changed the title WIP: use snakeyaml-engine on java 8+ and legacy snakeyaml on Java 7 Support use of snakeyaml-engine on java 8+ and legacy snakeyaml on Java 7 Feb 12, 2026
@mcculls mcculls removed the wip label Feb 12, 2026
@mcculls mcculls marked this pull request as ready for review February 12, 2026 12:13
@mcculls mcculls requested a review from a team as a code owner February 12, 2026 12:13
@mcculls mcculls requested a review from carlosroman March 18, 2026 13:11
@carlosroman
Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351
Copy link
Copy Markdown

gh-worker-devflow-routing-ef8351 bot commented Apr 10, 2026

View all feedbacks in Devflow UI.

2026-04-10 13:40:19 UTC ℹ️ Start processing command /merge


2026-04-10 13:40:24 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 14m (p90).


2026-04-10 13:53:01 UTC ℹ️ MergeQueue: This merge request was merged

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants