This is an automated email from the ASF dual-hosted git repository.
jamesbognar pushed a commit to branch docs
in repository https://gitbox.apache.org/repos/asf/juneau.git
The following commit(s) were added to refs/heads/docs by this push:
new 1cb3352e94 TODO-251: Reword 10.0.0 notes for dead fileCharset
builder-API removal
1cb3352e94 is described below
commit 1cb3352e94c29da60de70902af7dda7eb31e1292
Author: James Bognar <[email protected]>
AuthorDate: Thu Jul 16 14:08:42 2026 -0400
TODO-251: Reword 10.0.0 notes for dead fileCharset builder-API removal
Follow-up to TODO-248 (stream-only marshaller I/O). Documents removal of the
dead fileCharset(...) serializer/parser builder methods, getFileCharset()
getters, and @SerializerConfig/@ParserConfig fileCharset attributes:
- Reword the 10.0.0 release note and add a Breaking-Changes entry
- Update the V10 migration-guide wording
Co-authored-by: Cursor <[email protected]>
---
pages/release-notes/10.0.0.md | 9 ++++++++-
pages/topics/27.V10MigrationGuide.md | 5 +++--
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/pages/release-notes/10.0.0.md b/pages/release-notes/10.0.0.md
index 4ec341450e..a24c6b2dc6 100644
--- a/pages/release-notes/10.0.0.md
+++ b/pages/release-notes/10.0.0.md
@@ -705,7 +705,14 @@ _TBD — to be filled in as development continues._
JsonSerializer.DEFAULT.serialize(bean, sw);
String json = sw.toString();
```
- - The `SerializerPipe` / `ParserPipe` classes are **retained** (they still
own the stream close/flush lifecycle, charset decoding, debug capture, and
position tracking for the surviving stream types) — only their
`File`/`StringBuilder` handling and the now-dead `fileCharset` pipe-constructor
argument were removed. The `fileCharset(...)` builder setting still exists but
is now a no-op for the narrowed I/O surface.
+ - The `SerializerPipe` / `ParserPipe` classes are **retained** (they still
own the stream close/flush lifecycle, charset decoding, debug capture, and
position tracking for the surviving stream types) — only their
`File`/`StringBuilder` handling and the now-dead `fileCharset` pipe-constructor
argument were removed. The `fileCharset(...)` builder setting was subsequently
removed as well (see the next entry).
+
+- **`fileCharset(...)` serializer/parser builder setting and
`getFileCharset()` getter removed (TODO-251).** With the TODO-248 stream-only
I/O change (above), the file-charset setting became a dead no-op — the narrowed
`SerializerPipe`/`ParserPipe` plumbing no longer reads it. It has now been
removed entirely:
+ - **Builder methods removed:**
`WriterSerializer.Builder#fileCharset(Charset)`,
`ReaderParser.Builder#fileCharset(Charset)`, and the session-builder variants
`WriterSerializerSession.Builder#fileCharset(Charset)` /
`ReaderParserSession.Builder#fileCharset(Charset)`.
+ - **Getters removed:** `WriterSerializer#getFileCharset()` /
`ReaderParser#getFileCharset()` (protected) and
`WriterSerializerSession#getFileCharset()` /
`ReaderParserSession#getFileCharset()` (public).
+ - **Annotation attributes removed:** `@SerializerConfig(fileCharset=...)`
and `@ParserConfig(fileCharset=...)`.
+ - **Session property keys removed:** the `"fileCharset"` (and qualified
`"WriterSerializerSession.fileCharset"` / `"ReaderParserSession.fileCharset"`)
session `property(...)` keys are no longer recognized.
+ - **Migration:** none needed for correctness — the setting had no effect
after TODO-248. Remove any lingering `.fileCharset(...)` builder calls or
`@SerializerConfig`/`@ParserConfig` `fileCharset` attributes. If you relied on
`File`-charset behavior, decode the `Reader`/`InputStream` yourself before
passing it in (see the `File` migration snippet above).
_Other entries TBD — to be filled in before release. See also the major
version bump note above._
diff --git a/pages/topics/27.V10MigrationGuide.md
b/pages/topics/27.V10MigrationGuide.md
index 6921886d56..538c179389 100644
--- a/pages/topics/27.V10MigrationGuide.md
+++ b/pages/topics/27.V10MigrationGuide.md
@@ -189,8 +189,9 @@ Wrap it yourself:
`SerializerPipe` / `ParserPipe` are retained (they still own the stream
close/flush lifecycle, charset decoding, debug
capture, and position tracking) — only their `File` / `StringBuilder` handling
and the now-dead `fileCharset`
-pipe-constructor argument were removed. The `fileCharset(...)` builder
setting still exists but is now a no-op for the
-narrowed I/O surface.
+pipe-constructor argument were removed. The `fileCharset(...)` builder
setting (and its `getFileCharset()` getter and
+`@SerializerConfig`/`@ParserConfig` `fileCharset` attributes) — a dead no-op
after this stream-only change — has since
+been removed entirely. Remove any lingering `.fileCharset(...)` calls; no
behavioral change results.
## Bean→Marshalled Renames
