You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publish Jackson 3 module under new groupId org.msgpack.jackson3
Restructure the module layout per PR review feedback (JLBP-6): instead of
renaming the Jackson 2 artifact to jackson2-dataformat-msgpack and giving
Jackson 3 the unqualified jackson-dataformat-msgpack artifactId, rename the
Maven coordinates and the Java package together:
- Jackson 2 (msgpack-jackson): keeps org.msgpack:jackson-dataformat-msgpack
and the org.msgpack.jackson.dataformat package, exactly as 0.9.x. Existing
users need no changes. Maintenance mode: Jackson 2.x bumps and bug fixes only.
- Jackson 3 (msgpack-jackson3): published as
org.msgpack.jackson3:jackson-dataformat-msgpack with the
org.msgpack.jackson3.dataformat package, mirroring Jackson's own 2->3
groupId rename (com.fasterxml.jackson.dataformat -> tools.jackson.dataformat).
Because the two artifacts share the same fully-qualified class names in
neither direction, they can coexist on one classpath, and dependency
resolution can never silently replace the Jackson 2 classes with Jackson 3
ones (or vice versa). The 1.0.0 version bump is no longer needed.
Both sbt subprojects now share the module name jackson-dataformat-msgpack,
so the Jackson 3 project overrides outputPath to keep sbt 2 build output
directories from overlapping.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C4Sp7Q2urgnYfuNXK2fVFm
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,12 +57,12 @@ msgpack-java supports serialization and deserialization of Java objects through
57
57
58
58
Two artifacts are published depending on which Jackson major version your project uses:
59
59
60
-
| Jackson version |Artifact| Requirements |
61
-
| --- | --- | --- |
62
-
| Jackson 3.x |[`jackson-dataformat-msgpack`](https://github.com/msgpack/msgpack-java/blob/main/msgpack-jackson/README.md)(1.x)| Java 17+ |
63
-
| Jackson 2.x |[`jackson2-dataformat-msgpack`](https://github.com/msgpack/msgpack-java/blob/main/msgpack-jackson2/README.md) (maintenance mode) | Java 8+ |
60
+
| Jackson version |groupId | artifactId | Java package| Requirements |
61
+
| --- | --- | --- | --- | --- |
62
+
| Jackson 3.x |`org.msgpack.jackson3`|[`jackson-dataformat-msgpack`](https://github.com/msgpack/msgpack-java/blob/main/msgpack-jackson3/README.md)|`org.msgpack.jackson3.dataformat`| Java 17+ |
63
+
| Jackson 2.x |`org.msgpack`|[`jackson-dataformat-msgpack`](https://github.com/msgpack/msgpack-java/blob/main/msgpack-jackson/README.md) (maintenance mode)|`org.msgpack.jackson.dataformat`| Java 8+ |
64
64
65
-
Since msgpack-java 1.0.0, `jackson-dataformat-msgpack` targets Jackson 3.x. If your project still depends on Jackson 2.x, either stay on `jackson-dataformat-msgpack` 0.9.x or switch to `jackson2-dataformat-msgpack` to keep receiving msgpack-core updates (only the artifactId changes; the Java package is the same). See each module's README for install instructions and usage details.
65
+
The Jackson 2.x artifact keeps the same Maven coordinates and Java package as before, so existing users need no changes. The Jackson 3.x support is published under a new groupId (`org.msgpack.jackson3`) with a new Java package, following the same convention as Jackson itself (`com.fasterxml.jackson.dataformat` → `tools.jackson.dataformat`); renaming the Maven coordinates and the Java package together allows both artifacts to coexist on the same classpath for incremental migration. See each module's README for install instructions and usage details.
0 commit comments