Etienne Dysli Metref

I've hit a similar issue on Linux trying to print the layout cards. Hitting `ctrl-P` crashes Chrysalis with: ``` Crashing due to FD ownership violation: #0 0x55c46cb0ba93 #1 0x55c46cbb919c #2...

I tried again with Chrysalis version 0.11.6 using the print button, unfortunately the issue is still present. The OS print dialogue briefly appears, then the application crashes.

Please fix this, it makes this SDK harder to use with Spring Boot since both instantiate `ObjectMapper`s. Which one is actually used? If it were configurable, I'd be able to...

duplicates #207 see also #206

> You are completely right, this is an issue with `org.testcontainers.junit-jupiter` bringing in the transitive `org.junit.jupiter:junit-jupiter-api:jar:5.8.2` dependency. Would switching the dependency declaration `api 'org.junit.jupiter:junit-jupiter-api:5.9.1'` to `implementation` help? Gradle's Java Library...

@eddumelendez it will indeed break projects relying on this transitive dependency. However, they shouldn't do this and instead declare a dependency on `org.junit.jupiter:junit-jupiter` -- just like @ilgrosso did -- since...

Thanks @kiview for the nice example. Taking inspiration from it, I reworked how JUnit artifacts are included, in order to avoid using the `api` configuration, see #5985.

I'd like to give this one a try. :) Is updating the Javadoc on `org.junit.platform.launcher.TestExecutionListener` enough, or is there another guide to update as well?

I've tried with `Chrysalis-pr-1194.AppImage` as you suggested and the crash no longer happens. :) The print dialogue appeared after hitting `Ctrl-P` and it let me print to a file.

I think the release notes should mention that projects using `org.testcontainers:junit-jupiter` should ensure they declare a direct dependency on `org.junit.jupiter:junit-jupiter`. How can we do this?