Add missing EOF checks in MultiDelimiterInterpolatorFilterReaderLineEnding.read()

[elharo]

The escape-detection loop (line 223) and delimiter-detection loop (line 246)
were missing ch == -1 checks. When EOF is reached mid-token, (char) -1
produces 0xFFFF which gets appended to the key StringBuilder as garbage.
The equivalent single-delimiter class InterpolatorFilterReaderLineEnding
already has these checks.

fixes #349

[Copilot]

Pull request overview

This pull request fixes EOF handling in MultiDelimiterInterpolatorFilterReaderLineEnding.read() so that reaching end-of-stream while matching an escape string or delimiter begin token no longer results in 0xFFFF being appended to the output.

Changes:

• Add explicit ch == -1 checks in the escape-string and begin-token matching loops.
• Prevent appending (char) -1 to the output buffer during escape handling.
• Add a regression test covering EOF immediately after an escape character.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/main/java/org/apache/maven/shared/filtering/MultiDelimiterInterpolatorFilterReaderLineEnding.java	Adds EOF guards during token detection and avoids appending (char)-1 when EOF occurs while processing an escape sequence.
src/test/java/org/apache/maven/shared/filtering/MultiDelimiterInterpolatorFilterReaderLineEndingTest.java	Adds a regression test ensuring EOF after an escape char does not emit a garbage 0xFFFF character.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.