dependabot[bot] opened a new pull request, #1550: URL: https://github.com/apache/maven-mvnd/pull/1550
Bumps `jline.version` from 3.30.7 to 4.0.4. Updates `org.jline:jline-terminal` from 3.30.7 to 4.0.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jline/jline3/releases";>org.jline:jline-terminal's releases</a>.</em></p> <blockquote> <h2>JLine 4.0.4</h2> <h2>Bug Fixes</h2> <ul> <li>Disable grapheme cluster mode probe (DECRQM) on Windows <code>PosixSysTerminal</code> to prevent escape sequence <code>[?2027$p</code> from leaking into subprocess output on Cygwin/MSYSTEM environments (<a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a>) <ul> <li>This is a follow-up to the 4.0.3 fix which was insufficient — the <code>isSystemStream()</code> check was unreliable on Windows MSYSTEM environments</li> </ul> </li> </ul> <h2>Full Changelog</h2> <p><a href="https://github.com/jline/jline3/compare/4.0.3...4.0.4";>https://github.com/jline/jline3/compare/4.0.3...4.0.4</a></p> <h2>JLine 4.0.3</h2> <p>Bugfix release fixing output corruption on Windows when using Cygwin/MSYSTEM (Git Bash).</p> <h3>Bug Fixes</h3> <ul> <li><strong>Fix grapheme cluster probe corrupting output on Windows</strong> — On Windows with Cygwin/MSYSTEM (Git Bash), the DECRQM mode 2027 probe (<code>\e[?2027$p</code>) was written to a raw <code>FileDescriptor</code> (stdout/stderr) rather than a real PTY device. When the output was piped (e.g. subprocess with captured output), this escape sequence leaked into the process output, corrupting downstream consumers. The probe is now skipped when the <code>ExecPty</code> output stream is not connected to a real terminal. Interactive Cygwin/MSYSTEM terminals that support mode 2027 are unaffected. (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> </ul> <h2>JLine 4.0.2</h2> <p>Bugfix release fixing Maven 3/Gradle compatibility and JNI terminal provider issues.</p> <blockquote> <p><strong>Note:</strong> Users of 4.0.0 and 4.0.1 should upgrade to 4.0.2. Both prior releases had broken consumer POMs that prevented Maven 3 and Gradle from resolving JLine dependencies.</p> </blockquote> <h3>Bug Fixes</h3> <ul> <li><strong>Fix Maven 3/Gradle compatibility</strong> — Consumer POMs now use <code>modelVersion</code> 4.0.0 with no <code><parent></code> reference, making them consumable by Maven 3 and Gradle. Previously, child module POMs referenced <code>jline-parent</code> which used <code>modelVersion</code> 4.1.0, causing resolution failures. (<a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a>, <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1688";>#1688</a>, workaround for <a href="https://redirect.github.com/apache/maven/issues/11772";>apache/maven#11772</a>)</li> <li><strong>Fix JNI terminal failing to load on JDK 21.0.10+</strong> — <code>Module.isNativeAccessEnabled()</code> was backported to some JDK 21 builds (e.g. 21.0.10), causing a false <code>UnsupportedOperationException</code> since the method returns <code>false</code> even though JNI works without <code>--enable-native-access</code>. JNI native access restrictions are only enforced from JDK 24+, so the check is now skipped on earlier versions. (<a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> </ul> <h3>Dependency Updates</h3> <ul> <li>Bump spotless-maven-plugin from 3.2.1 to 3.3.0</li> <li>Bump native-maven-plugin from 0.11.4 to 0.11.5</li> <li>Bump maven-shade-plugin from 3.6.0 to 3.6.2</li> <li>Bump maven-resources-plugin from 3.3.1 to 3.5.0</li> </ul> <h2>JLine 4.0.1</h2> <p>Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</p> <p>fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</p> <h2>JLine 4.0.0</h2> <h2>Breaking Changes</h2> <ul> <li><strong>Maven 4 requirement</strong>: Upgraded to POM model 4.1.0</li> <li><strong>Java 11+ required</strong>: Raised minimum runtime requirement from Java 8 to Java 11</li> <li><strong>JPMS migration</strong>: Complete Java Platform Module System migration with Java 24 support (<a href="https://redirect.github.com/jline/jline3/issues/1374";>#1374</a>)</li> <li><strong>JNA provider removed</strong>: Only JNI and FFM terminal providers remain</li> <li><strong>Removed deprecated elements</strong>: All previously deprecated APIs removed (<a href="https://redirect.github.com/jline/jline3/issues/1384";>#1384</a>)</li> <li><strong>Standard Java SPI</strong>: Terminal providers now use standard Java ServiceLoader (<a href="https://redirect.github.com/jline/jline3/issues/1523";>#1523</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jline/jline3/commit/2b64601ad9b61caca011c1cc8dc009a16b2695da";><code>2b64601</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a> from jline/fix/grapheme-probe-windows-2</li> <li><a href="https://github.com/jline/jline3/commit/75cfb61c6b8a3b557fd24c097dbae9d5f35f0bbc";><code>75cfb61</code></a> fix: Disable grapheme cluster probe on Windows PosixSysTerminal</li> <li><a href="https://github.com/jline/jline3/commit/edd28d281db006a6cbf08f1c9594d138802e706e";><code>edd28d2</code></a> fix: Skip grapheme cluster probe on Windows to prevent output corruption (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> <li><a href="https://github.com/jline/jline3/commit/2505581ef6215cafeab02586c0068b9b0cd7058a";><code>2505581</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a> from jline/fix/consumer-pom-flatten-location</li> <li><a href="https://github.com/jline/jline3/commit/397f4348425b215c6aa7d96790d602579bea4b3c";><code>397f434</code></a> fix: Move consumer POM flattening config to .mvn/maven.properties</li> <li><a href="https://github.com/jline/jline3/commit/f6a7673a2ec10cd20849e01ff4f669eea9eb13fb";><code>f6a7673</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</li> <li><a href="https://github.com/jline/jline3/commit/953265921eba6b35d3a873070815ea1a582977eb";><code>9532659</code></a> fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> <li><a href="https://github.com/jline/jline3/commit/786a040964c263b2342c4e31b3a2465fdc03b450";><code>786a040</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a> from jline/fix/consumer-pom-flatten</li> <li><a href="https://github.com/jline/jline3/commit/dc4931bfc4e774b2544c5f6a305b727aa3d2a1cd";><code>dc4931b</code></a> fix: Enable consumer POM flattening to fix Maven 3/Gradle compatibility (work...</li> <li><a href="https://github.com/jline/jline3/commit/4e7d7e15070347c58a52ed1366ab6d8cc52b2fb9";><code>4e7d7e1</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1687";>#1687</a> from jline/dependabot/maven/master/org.apache.maven....</li> <li>Additional commits viewable in <a href="https://github.com/jline/jline3/compare/jline-3.30.7...4.0.4";>compare view</a></li> </ul> </details> <br /> Updates `org.jline:jline-terminal-jni` from 3.30.7 to 4.0.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jline/jline3/releases";>org.jline:jline-terminal-jni's releases</a>.</em></p> <blockquote> <h2>JLine 4.0.4</h2> <h2>Bug Fixes</h2> <ul> <li>Disable grapheme cluster mode probe (DECRQM) on Windows <code>PosixSysTerminal</code> to prevent escape sequence <code>[?2027$p</code> from leaking into subprocess output on Cygwin/MSYSTEM environments (<a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a>) <ul> <li>This is a follow-up to the 4.0.3 fix which was insufficient — the <code>isSystemStream()</code> check was unreliable on Windows MSYSTEM environments</li> </ul> </li> </ul> <h2>Full Changelog</h2> <p><a href="https://github.com/jline/jline3/compare/4.0.3...4.0.4";>https://github.com/jline/jline3/compare/4.0.3...4.0.4</a></p> <h2>JLine 4.0.3</h2> <p>Bugfix release fixing output corruption on Windows when using Cygwin/MSYSTEM (Git Bash).</p> <h3>Bug Fixes</h3> <ul> <li><strong>Fix grapheme cluster probe corrupting output on Windows</strong> — On Windows with Cygwin/MSYSTEM (Git Bash), the DECRQM mode 2027 probe (<code>\e[?2027$p</code>) was written to a raw <code>FileDescriptor</code> (stdout/stderr) rather than a real PTY device. When the output was piped (e.g. subprocess with captured output), this escape sequence leaked into the process output, corrupting downstream consumers. The probe is now skipped when the <code>ExecPty</code> output stream is not connected to a real terminal. Interactive Cygwin/MSYSTEM terminals that support mode 2027 are unaffected. (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> </ul> <h2>JLine 4.0.2</h2> <p>Bugfix release fixing Maven 3/Gradle compatibility and JNI terminal provider issues.</p> <blockquote> <p><strong>Note:</strong> Users of 4.0.0 and 4.0.1 should upgrade to 4.0.2. Both prior releases had broken consumer POMs that prevented Maven 3 and Gradle from resolving JLine dependencies.</p> </blockquote> <h3>Bug Fixes</h3> <ul> <li><strong>Fix Maven 3/Gradle compatibility</strong> — Consumer POMs now use <code>modelVersion</code> 4.0.0 with no <code><parent></code> reference, making them consumable by Maven 3 and Gradle. Previously, child module POMs referenced <code>jline-parent</code> which used <code>modelVersion</code> 4.1.0, causing resolution failures. (<a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a>, <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1688";>#1688</a>, workaround for <a href="https://redirect.github.com/apache/maven/issues/11772";>apache/maven#11772</a>)</li> <li><strong>Fix JNI terminal failing to load on JDK 21.0.10+</strong> — <code>Module.isNativeAccessEnabled()</code> was backported to some JDK 21 builds (e.g. 21.0.10), causing a false <code>UnsupportedOperationException</code> since the method returns <code>false</code> even though JNI works without <code>--enable-native-access</code>. JNI native access restrictions are only enforced from JDK 24+, so the check is now skipped on earlier versions. (<a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> </ul> <h3>Dependency Updates</h3> <ul> <li>Bump spotless-maven-plugin from 3.2.1 to 3.3.0</li> <li>Bump native-maven-plugin from 0.11.4 to 0.11.5</li> <li>Bump maven-shade-plugin from 3.6.0 to 3.6.2</li> <li>Bump maven-resources-plugin from 3.3.1 to 3.5.0</li> </ul> <h2>JLine 4.0.1</h2> <p>Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</p> <p>fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</p> <h2>JLine 4.0.0</h2> <h2>Breaking Changes</h2> <ul> <li><strong>Maven 4 requirement</strong>: Upgraded to POM model 4.1.0</li> <li><strong>Java 11+ required</strong>: Raised minimum runtime requirement from Java 8 to Java 11</li> <li><strong>JPMS migration</strong>: Complete Java Platform Module System migration with Java 24 support (<a href="https://redirect.github.com/jline/jline3/issues/1374";>#1374</a>)</li> <li><strong>JNA provider removed</strong>: Only JNI and FFM terminal providers remain</li> <li><strong>Removed deprecated elements</strong>: All previously deprecated APIs removed (<a href="https://redirect.github.com/jline/jline3/issues/1384";>#1384</a>)</li> <li><strong>Standard Java SPI</strong>: Terminal providers now use standard Java ServiceLoader (<a href="https://redirect.github.com/jline/jline3/issues/1523";>#1523</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jline/jline3/commit/2b64601ad9b61caca011c1cc8dc009a16b2695da";><code>2b64601</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a> from jline/fix/grapheme-probe-windows-2</li> <li><a href="https://github.com/jline/jline3/commit/75cfb61c6b8a3b557fd24c097dbae9d5f35f0bbc";><code>75cfb61</code></a> fix: Disable grapheme cluster probe on Windows PosixSysTerminal</li> <li><a href="https://github.com/jline/jline3/commit/edd28d281db006a6cbf08f1c9594d138802e706e";><code>edd28d2</code></a> fix: Skip grapheme cluster probe on Windows to prevent output corruption (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> <li><a href="https://github.com/jline/jline3/commit/2505581ef6215cafeab02586c0068b9b0cd7058a";><code>2505581</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a> from jline/fix/consumer-pom-flatten-location</li> <li><a href="https://github.com/jline/jline3/commit/397f4348425b215c6aa7d96790d602579bea4b3c";><code>397f434</code></a> fix: Move consumer POM flattening config to .mvn/maven.properties</li> <li><a href="https://github.com/jline/jline3/commit/f6a7673a2ec10cd20849e01ff4f669eea9eb13fb";><code>f6a7673</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</li> <li><a href="https://github.com/jline/jline3/commit/953265921eba6b35d3a873070815ea1a582977eb";><code>9532659</code></a> fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> <li><a href="https://github.com/jline/jline3/commit/786a040964c263b2342c4e31b3a2465fdc03b450";><code>786a040</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a> from jline/fix/consumer-pom-flatten</li> <li><a href="https://github.com/jline/jline3/commit/dc4931bfc4e774b2544c5f6a305b727aa3d2a1cd";><code>dc4931b</code></a> fix: Enable consumer POM flattening to fix Maven 3/Gradle compatibility (work...</li> <li><a href="https://github.com/jline/jline3/commit/4e7d7e15070347c58a52ed1366ab6d8cc52b2fb9";><code>4e7d7e1</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1687";>#1687</a> from jline/dependabot/maven/master/org.apache.maven....</li> <li>Additional commits viewable in <a href="https://github.com/jline/jline3/compare/jline-3.30.7...4.0.4";>compare view</a></li> </ul> </details> <br /> Updates `org.jline:jline-terminal-ffm` from 3.30.7 to 4.0.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jline/jline3/releases";>org.jline:jline-terminal-ffm's releases</a>.</em></p> <blockquote> <h2>JLine 4.0.4</h2> <h2>Bug Fixes</h2> <ul> <li>Disable grapheme cluster mode probe (DECRQM) on Windows <code>PosixSysTerminal</code> to prevent escape sequence <code>[?2027$p</code> from leaking into subprocess output on Cygwin/MSYSTEM environments (<a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a>) <ul> <li>This is a follow-up to the 4.0.3 fix which was insufficient — the <code>isSystemStream()</code> check was unreliable on Windows MSYSTEM environments</li> </ul> </li> </ul> <h2>Full Changelog</h2> <p><a href="https://github.com/jline/jline3/compare/4.0.3...4.0.4";>https://github.com/jline/jline3/compare/4.0.3...4.0.4</a></p> <h2>JLine 4.0.3</h2> <p>Bugfix release fixing output corruption on Windows when using Cygwin/MSYSTEM (Git Bash).</p> <h3>Bug Fixes</h3> <ul> <li><strong>Fix grapheme cluster probe corrupting output on Windows</strong> — On Windows with Cygwin/MSYSTEM (Git Bash), the DECRQM mode 2027 probe (<code>\e[?2027$p</code>) was written to a raw <code>FileDescriptor</code> (stdout/stderr) rather than a real PTY device. When the output was piped (e.g. subprocess with captured output), this escape sequence leaked into the process output, corrupting downstream consumers. The probe is now skipped when the <code>ExecPty</code> output stream is not connected to a real terminal. Interactive Cygwin/MSYSTEM terminals that support mode 2027 are unaffected. (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> </ul> <h2>JLine 4.0.2</h2> <p>Bugfix release fixing Maven 3/Gradle compatibility and JNI terminal provider issues.</p> <blockquote> <p><strong>Note:</strong> Users of 4.0.0 and 4.0.1 should upgrade to 4.0.2. Both prior releases had broken consumer POMs that prevented Maven 3 and Gradle from resolving JLine dependencies.</p> </blockquote> <h3>Bug Fixes</h3> <ul> <li><strong>Fix Maven 3/Gradle compatibility</strong> — Consumer POMs now use <code>modelVersion</code> 4.0.0 with no <code><parent></code> reference, making them consumable by Maven 3 and Gradle. Previously, child module POMs referenced <code>jline-parent</code> which used <code>modelVersion</code> 4.1.0, causing resolution failures. (<a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a>, <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1688";>#1688</a>, workaround for <a href="https://redirect.github.com/apache/maven/issues/11772";>apache/maven#11772</a>)</li> <li><strong>Fix JNI terminal failing to load on JDK 21.0.10+</strong> — <code>Module.isNativeAccessEnabled()</code> was backported to some JDK 21 builds (e.g. 21.0.10), causing a false <code>UnsupportedOperationException</code> since the method returns <code>false</code> even though JNI works without <code>--enable-native-access</code>. JNI native access restrictions are only enforced from JDK 24+, so the check is now skipped on earlier versions. (<a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> </ul> <h3>Dependency Updates</h3> <ul> <li>Bump spotless-maven-plugin from 3.2.1 to 3.3.0</li> <li>Bump native-maven-plugin from 0.11.4 to 0.11.5</li> <li>Bump maven-shade-plugin from 3.6.0 to 3.6.2</li> <li>Bump maven-resources-plugin from 3.3.1 to 3.5.0</li> </ul> <h2>JLine 4.0.1</h2> <p>Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</p> <p>fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</p> <h2>JLine 4.0.0</h2> <h2>Breaking Changes</h2> <ul> <li><strong>Maven 4 requirement</strong>: Upgraded to POM model 4.1.0</li> <li><strong>Java 11+ required</strong>: Raised minimum runtime requirement from Java 8 to Java 11</li> <li><strong>JPMS migration</strong>: Complete Java Platform Module System migration with Java 24 support (<a href="https://redirect.github.com/jline/jline3/issues/1374";>#1374</a>)</li> <li><strong>JNA provider removed</strong>: Only JNI and FFM terminal providers remain</li> <li><strong>Removed deprecated elements</strong>: All previously deprecated APIs removed (<a href="https://redirect.github.com/jline/jline3/issues/1384";>#1384</a>)</li> <li><strong>Standard Java SPI</strong>: Terminal providers now use standard Java ServiceLoader (<a href="https://redirect.github.com/jline/jline3/issues/1523";>#1523</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jline/jline3/commit/2b64601ad9b61caca011c1cc8dc009a16b2695da";><code>2b64601</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a> from jline/fix/grapheme-probe-windows-2</li> <li><a href="https://github.com/jline/jline3/commit/75cfb61c6b8a3b557fd24c097dbae9d5f35f0bbc";><code>75cfb61</code></a> fix: Disable grapheme cluster probe on Windows PosixSysTerminal</li> <li><a href="https://github.com/jline/jline3/commit/edd28d281db006a6cbf08f1c9594d138802e706e";><code>edd28d2</code></a> fix: Skip grapheme cluster probe on Windows to prevent output corruption (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> <li><a href="https://github.com/jline/jline3/commit/2505581ef6215cafeab02586c0068b9b0cd7058a";><code>2505581</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a> from jline/fix/consumer-pom-flatten-location</li> <li><a href="https://github.com/jline/jline3/commit/397f4348425b215c6aa7d96790d602579bea4b3c";><code>397f434</code></a> fix: Move consumer POM flattening config to .mvn/maven.properties</li> <li><a href="https://github.com/jline/jline3/commit/f6a7673a2ec10cd20849e01ff4f669eea9eb13fb";><code>f6a7673</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</li> <li><a href="https://github.com/jline/jline3/commit/953265921eba6b35d3a873070815ea1a582977eb";><code>9532659</code></a> fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> <li><a href="https://github.com/jline/jline3/commit/786a040964c263b2342c4e31b3a2465fdc03b450";><code>786a040</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a> from jline/fix/consumer-pom-flatten</li> <li><a href="https://github.com/jline/jline3/commit/dc4931bfc4e774b2544c5f6a305b727aa3d2a1cd";><code>dc4931b</code></a> fix: Enable consumer POM flattening to fix Maven 3/Gradle compatibility (work...</li> <li><a href="https://github.com/jline/jline3/commit/4e7d7e15070347c58a52ed1366ab6d8cc52b2fb9";><code>4e7d7e1</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1687";>#1687</a> from jline/dependabot/maven/master/org.apache.maven....</li> <li>Additional commits viewable in <a href="https://github.com/jline/jline3/compare/jline-3.30.7...4.0.4";>compare view</a></li> </ul> </details> <br /> Updates `org.jline:jline-native` from 3.30.7 to 4.0.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jline/jline3/releases";>org.jline:jline-native's releases</a>.</em></p> <blockquote> <h2>JLine 4.0.4</h2> <h2>Bug Fixes</h2> <ul> <li>Disable grapheme cluster mode probe (DECRQM) on Windows <code>PosixSysTerminal</code> to prevent escape sequence <code>[?2027$p</code> from leaking into subprocess output on Cygwin/MSYSTEM environments (<a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a>) <ul> <li>This is a follow-up to the 4.0.3 fix which was insufficient — the <code>isSystemStream()</code> check was unreliable on Windows MSYSTEM environments</li> </ul> </li> </ul> <h2>Full Changelog</h2> <p><a href="https://github.com/jline/jline3/compare/4.0.3...4.0.4";>https://github.com/jline/jline3/compare/4.0.3...4.0.4</a></p> <h2>JLine 4.0.3</h2> <p>Bugfix release fixing output corruption on Windows when using Cygwin/MSYSTEM (Git Bash).</p> <h3>Bug Fixes</h3> <ul> <li><strong>Fix grapheme cluster probe corrupting output on Windows</strong> — On Windows with Cygwin/MSYSTEM (Git Bash), the DECRQM mode 2027 probe (<code>\e[?2027$p</code>) was written to a raw <code>FileDescriptor</code> (stdout/stderr) rather than a real PTY device. When the output was piped (e.g. subprocess with captured output), this escape sequence leaked into the process output, corrupting downstream consumers. The probe is now skipped when the <code>ExecPty</code> output stream is not connected to a real terminal. Interactive Cygwin/MSYSTEM terminals that support mode 2027 are unaffected. (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> </ul> <h2>JLine 4.0.2</h2> <p>Bugfix release fixing Maven 3/Gradle compatibility and JNI terminal provider issues.</p> <blockquote> <p><strong>Note:</strong> Users of 4.0.0 and 4.0.1 should upgrade to 4.0.2. Both prior releases had broken consumer POMs that prevented Maven 3 and Gradle from resolving JLine dependencies.</p> </blockquote> <h3>Bug Fixes</h3> <ul> <li><strong>Fix Maven 3/Gradle compatibility</strong> — Consumer POMs now use <code>modelVersion</code> 4.0.0 with no <code><parent></code> reference, making them consumable by Maven 3 and Gradle. Previously, child module POMs referenced <code>jline-parent</code> which used <code>modelVersion</code> 4.1.0, causing resolution failures. (<a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a>, <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1688";>#1688</a>, workaround for <a href="https://redirect.github.com/apache/maven/issues/11772";>apache/maven#11772</a>)</li> <li><strong>Fix JNI terminal failing to load on JDK 21.0.10+</strong> — <code>Module.isNativeAccessEnabled()</code> was backported to some JDK 21 builds (e.g. 21.0.10), causing a false <code>UnsupportedOperationException</code> since the method returns <code>false</code> even though JNI works without <code>--enable-native-access</code>. JNI native access restrictions are only enforced from JDK 24+, so the check is now skipped on earlier versions. (<a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a>, fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> </ul> <h3>Dependency Updates</h3> <ul> <li>Bump spotless-maven-plugin from 3.2.1 to 3.3.0</li> <li>Bump native-maven-plugin from 0.11.4 to 0.11.5</li> <li>Bump maven-shade-plugin from 3.6.0 to 3.6.2</li> <li>Bump maven-resources-plugin from 3.3.1 to 3.5.0</li> </ul> <h2>JLine 4.0.1</h2> <p>Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</p> <p>fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</p> <h2>JLine 4.0.0</h2> <h2>Breaking Changes</h2> <ul> <li><strong>Maven 4 requirement</strong>: Upgraded to POM model 4.1.0</li> <li><strong>Java 11+ required</strong>: Raised minimum runtime requirement from Java 8 to Java 11</li> <li><strong>JPMS migration</strong>: Complete Java Platform Module System migration with Java 24 support (<a href="https://redirect.github.com/jline/jline3/issues/1374";>#1374</a>)</li> <li><strong>JNA provider removed</strong>: Only JNI and FFM terminal providers remain</li> <li><strong>Removed deprecated elements</strong>: All previously deprecated APIs removed (<a href="https://redirect.github.com/jline/jline3/issues/1384";>#1384</a>)</li> <li><strong>Standard Java SPI</strong>: Terminal providers now use standard Java ServiceLoader (<a href="https://redirect.github.com/jline/jline3/issues/1523";>#1523</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jline/jline3/commit/2b64601ad9b61caca011c1cc8dc009a16b2695da";><code>2b64601</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1696";>#1696</a> from jline/fix/grapheme-probe-windows-2</li> <li><a href="https://github.com/jline/jline3/commit/75cfb61c6b8a3b557fd24c097dbae9d5f35f0bbc";><code>75cfb61</code></a> fix: Disable grapheme cluster probe on Windows PosixSysTerminal</li> <li><a href="https://github.com/jline/jline3/commit/edd28d281db006a6cbf08f1c9594d138802e706e";><code>edd28d2</code></a> fix: Skip grapheme cluster probe on Windows to prevent output corruption (<a href="https://redirect.github.com/jline/jline3/issues/1695";>#1695</a>)</li> <li><a href="https://github.com/jline/jline3/commit/2505581ef6215cafeab02586c0068b9b0cd7058a";><code>2505581</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1694";>#1694</a> from jline/fix/consumer-pom-flatten-location</li> <li><a href="https://github.com/jline/jline3/commit/397f4348425b215c6aa7d96790d602579bea4b3c";><code>397f434</code></a> fix: Move consumer POM flattening config to .mvn/maven.properties</li> <li><a href="https://github.com/jline/jline3/commit/f6a7673a2ec10cd20849e01ff4f669eea9eb13fb";><code>f6a7673</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1692";>#1692</a> from jline/fix/jni-native-access-check-1689</li> <li><a href="https://github.com/jline/jline3/commit/953265921eba6b35d3a873070815ea1a582977eb";><code>9532659</code></a> fix: Skip JNI native access check on JDK < 24 (fixes <a href="https://redirect.github.com/jline/jline3/issues/1689";>#1689</a>)</li> <li><a href="https://github.com/jline/jline3/commit/786a040964c263b2342c4e31b3a2465fdc03b450";><code>786a040</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1691";>#1691</a> from jline/fix/consumer-pom-flatten</li> <li><a href="https://github.com/jline/jline3/commit/dc4931bfc4e774b2544c5f6a305b727aa3d2a1cd";><code>dc4931b</code></a> fix: Enable consumer POM flattening to fix Maven 3/Gradle compatibility (work...</li> <li><a href="https://github.com/jline/jline3/commit/4e7d7e15070347c58a52ed1366ab6d8cc52b2fb9";><code>4e7d7e1</code></a> Merge pull request <a href="https://redirect.github.com/jline/jline3/issues/1687";>#1687</a> from jline/dependabot/maven/master/org.apache.maven....</li> <li>Additional commits viewable in <a href="https://github.com/jline/jline3/compare/jline-3.30.7...4.0.4";>compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
