Path to Jackson 3.0.0 #72
Replies: 4 comments 10 replies
-
|
/cc @k163377 @pjfanning @yawkat @yihtserns -- the new central planning page for Jackson 3.0.0. Trying to collect links to everything pertinent, keep updated. Especially interested in 3 Polls under "Things to Decide". |
Beta Was this translation helpful? Give feedback.
-
|
I should go tell community in Korea to vote. There is huge Java community here. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to enable |
Beta Was this translation helpful? Give feedback.
-
|
+1. Sounds counter-intuitive. |
Beta Was this translation helpful? Give feedback.
-
|
If not yet done, could someone file issue like #4845 / #4846 for this setting? Then I (or anyone else actially) can create discussion here (like #77 / #78). And this allows for discussing pros and cons. Or if an issue already created, we can just create discussion, add links. I think it's a good idea to try to get more people involved giving their opinion by voting. |
Beta Was this translation helpful? Give feedback.
-
|
Will do |
Beta Was this translation helpful? Give feedback.
-
|
@k163377 @cowtowncoder |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Created databind issue, linked to from this discussion so we are good. |
Beta Was this translation helpful? Give feedback.
-
|
How about another one? Proposal for this one : Unifying testing structure/tools pre-Jackson 3 that I previously proposed in Jackson main repo. Benefits....
|
Beta Was this translation helpful? Give feedback.
-
|
Sounds good, +1: could you create a new |
Beta Was this translation helpful? Give feedback.
-
|
Yeah will do. |
Beta Was this translation helpful? Give feedback.
-
|
Just so we all now. We now have https://github.com/FasterXML/jackson-future-ideas/wiki/JSTEP-10. Planning and other detailed discussions may be done in FasterXML/jackson#249 |
Beta Was this translation helpful? Give feedback.
-
[ Another suggestion for writing 2 -> 3 migration guide ]I would like to suggest that we have 2 -> 3 migration guide here in this repo. |
Beta Was this translation helpful? Give feedback.
-
|
That would be useful, although probably easiest to write if and when someone does actual upgrade of a codebase. Need not be source code, could be Markdown file (like README.md etc), just stored as file and not Wiki page. |
Beta Was this translation helpful? Give feedback.
-
Goal of this Discussion
This Discussion is "uber-discussion" covering the high-level scope of what the official Jackson 3.0.0 Release should include, along with bit of status of the progress. Most of content will be links to other pages, issues, discussions in other repos (with actual Issues, for example).
Note that while most issues are hoped to be addressed by
3.0.0-rc1(the first pre-release), we may want to stage them across multiple RCs to follow "release early, release often" to get a tight feedback loop.Jackson 3.0.0: Requirements
To reach state where we are ready to publish the final 3.0.0, we have to tackle following things.
(note: this document is work-in-progress and will continue living -- it is not a static requirements document).
JSTEPs
See JSTEP Overview for an overview what JSTEPs are. They can be thought as an effort bigger than what a single Issue can cover, and are natural way to group such efforts.
For 3.0.0 we want to tackle most of them, specifically:
JsonNodeimprovementsJacksonExceptionNote that we can create new JTEPs and reconsider ones not completed.
Some JSTEPs are also for 2.x, not 3.0 (and others for later 3.x versions beyond initial one).
Of these, ones with specific urgency are:
JsonNodeimprovements -- mostly need to decide API, implementation relatively straight-forwardjava.util.Date/ Java 8 Date/Time / JodaThings to decide (polls!)
Here are things to decide on proposed changes: please vote if you have opinion on whether change suggested is desired.
You may also add comments explaining your reasoning, as well as upvote comments by others.
General
Changes to Feature defaults
DeserializationFeature. FAIL_ON_NULL_FOR_PRIMITIVES-- issue databind#4858Issues to work on in jackson-databind
Aside from decisions (or in some cases, related to), there are specific issues to work on.
"Most Wanted" Jackson issues
Of all open issues, a small subset has been labeled as "most-wanted" based on upvotes.
These may be considered for inclusion in 2.x as well, but some might require bigger changes.
Because of this, it would make sense to see if any could be added in 3.0.0-SNAPSHOT:
Issues labeled with '3.0'
Some issues have been labeled specifically as targeted to 3.0.0-SNAPSHOT release:
https://github.com/FasterXML/jackson-databind/issues?q=is%3Aissue+is%3Aopen+label%3A3.0
Issues labeled with '3.x'
Other issues have been labeled with
3.xto indicate "not possible/practical for 2.x, maybe one of 3.x releases", but not necessarily 3.0.0:https://github.com/FasterXML/jackson-databind/issues?q=is%3Aissue+is%3Aopen+label%3A3.x
Issues/Discussion for Other Modules
Beside
jackson-databindrepo, there are issues in other FasterXML Jackson repositories, labeled for ideally being included in 3.0.0-SNAPSHOT:Kotlin
Beta Was this translation helpful? Give feedback.
All reactions