We should consider including a module for Jackson 3.0. The catch is, it's not backwards compatible. The package names and groupId's have changed. However, that is a good thing as the two can coexist.
It might be as simple as adding a module dependency. However, I think we need to decide a couple things:

1. Do we want to make it a public module?
2. If not a public module, do we even want to do it until some other component, e.g. RESTEasy, might need it?

The current Jackson modules are public. I think this is because they are common API's and exposed to deployments. Allowing a deployment to bring in their own version could be a potential issues for things like RESTEasy.

Some thought will need to go into how this works with the jaxrs subsystem and RESTEasy. RESTEasy does not currently support Jackson 3, but may do so in a new module in the future.

Information about Jackson 3 https://github.com/FasterXML/jackson/wiki/Jackson-Release-3.0