Jackson 2.10.0 release process complete, except for an open issue with `jackson-annotations`

24 views
Skip to first unread message

Tatu Saloranta

unread,
Sep 26, 2019, 9:16:22 PM9/26/19
to jackson-announce, jackson-user, jacks...@googlegroups.com
As per title: 2.10.0 release process is otherwise complete, including
Scala module (big thanks to PJ), with one problem: 2.10.0 of
`jackson-annotations` is missing some artifacts:

https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.10.0/

and this may be problematic for some tools. I am trying to resolve
this with Sonatype, but so far have heard nothing from them.

-+ Tatu +-

Tatu Saloranta

unread,
Sep 27, 2019, 3:38:07 PM9/27/19
to jackson-announce, jackson-user, jacks...@googlegroups.com
Update (27-Sep-2019, 12:00 PST): Thanks to help by Sonatype Nexus
admins (Joel), the problem has been resolved, and the full Jackson
2.10.0 release should now be available from Maven Central.

If you do find issues with any of components, please let me know (on
mailing list, github issue, gitter).

Also: please try out 2.10.0 if you get a chance! It should be a solid
step forward; I am writing a Blog Post to overview major improvements,
including but not limited to "Safe Default Typing" (no more CVE patch
roulette), "JDK 9 module info" and "Builders for constructing
ObjectMapper, JsonFactory".

-+ Tatu +-

Steinar Bang

unread,
Oct 9, 2019, 4:41:14 PM10/9/19
to jacks...@googlegroups.com
I'm rebasing the apache karaf feature fix branches to 2.11 since I
missed the 2.10 train.
https://github.com/FasterXML/jackson-databind/issues/2434#issuecomment-530543759

The jackson-datatypes-collections repo doesn't have a 2.11 branch.

Should I rebase on master for the repos without a 2.11 branch? Or will
there be a 2.11 branch in all of the repos?

Thanks!


- Steinar



Tatu Saloranta

unread,
Oct 9, 2019, 4:50:50 PM10/9/19
to Steinar Bang, jacks...@googlegroups.com
I'll need to create that one, will push it now. Process is manual, and
I have done it for maybe half the repos so far.

-+ Tatu +-
> --
> You received this message because you are subscribed to the Google Groups "jackson-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jackson-dev...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/86o8yp646v.fsf_-_%40dod.no.

Steinar Bang

unread,
Oct 12, 2019, 4:04:43 AM10/12/19
to jacks...@googlegroups.com
>>>>> Tatu Saloranta <ta...@fasterxml.com>:

> I'll need to create that one, will push it now. Process is manual, and
> I have done it for maybe half the repos so far.

Note: The jackson-jr pom of the 2.11 branch still refers to 2.10.0 of
jackson-base:
https://github.com/FasterXML/jackson-jr/blob/2.11/pom.xml#L6

(For the rebase of the karaf feature branches this means that jackson-jr
doesn't see the karaf-maven-plugin configuration i've put into
jackson-parent. It needs 2.11.0-SNAPSHOT for that)

Steinar Bang

unread,
Oct 12, 2019, 4:17:21 AM10/12/19
to jacks...@googlegroups.com
Just a small status report on the promised karaf feature PRs:

I had something appearently working against the 2.10 branches but I
didn't manage to the the PRs ready before the 2.10 train left the
platform, so I had to rebase to 2.11.

The primary karaf maintainer has also expressed interest in QAing the
changes, but will wait until after the 2.11 rebase to do so.

So the current plan, is:
1. rebase the fix branches of the jackson repos to the 2.11 branches of
the repos (this is where I'm currently at)
2. smoke test the karaf features (basicaly verify that the OSGi bundles
load in apache karaf)
3. submit the changes for QA with the karaf maintainer
4. apply the changes from that QA, with the necessary smoke testing
5. create the PRs and submit them, plan for submission
1. write a comment that I'm starting in the issue that started
this[1]
2. submit the PRs the order already in the issue
3. write a new comment in the first issue that PR submission is
complete

References:
[1] <https://github.com/FasterXML/jackson-databind/issues/2434>



Tatu Saloranta

unread,
Oct 12, 2019, 12:39:06 PM10/12/19
to Steinar Bang, jacks...@googlegroups.com
Thank you for pointing that out was an oversight.
I have to use mvn version:set plugin to update multi-module repos, but
had forgotten to update base. Done now, pushed snapshot.

-+ Tatu +-

Tatu Saloranta

unread,
Oct 12, 2019, 1:33:32 PM10/12/19
to Steinar Bang, jacks...@googlegroups.com
On Sat, Oct 12, 2019 at 1:17 AM Steinar Bang <s...@dod.no> wrote:
>
> Just a small status report on the promised karaf feature PRs:
>
> I had something appearently working against the 2.10 branches but I
> didn't manage to the the PRs ready before the 2.10 train left the
> platform, so I had to rebase to 2.11.

This was partly my fault, too, since I really wanted to get 2.10
release out before end of September, so that Spring releases could use
it.
But compared to 2.10, I want 2.11 to be completed much faster, more
similar to 1.x minor release schedule: ideally release candidates by
end of 2019, minor release maybe in January 2020.

> The primary karaf maintainer has also expressed interest in QAing the
> changes, but will wait until after the 2.11 rebase to do so.

This sounds good.

> So the current plan, is:
> 1. rebase the fix branches of the jackson repos to the 2.11 branches of
> the repos (this is where I'm currently at)
> 2. smoke test the karaf features (basicaly verify that the OSGi bundles
> load in apache karaf)
> 3. submit the changes for QA with the karaf maintainer
> 4. apply the changes from that QA, with the necessary smoke testing
> 5. create the PRs and submit them, plan for submission
> 1. write a comment that I'm starting in the issue that started
> this[1]
> 2. submit the PRs the order already in the issue
> 3. write a new comment in the first issue that PR submission is
> complete
>
> References:
> [1] <https://github.com/FasterXML/jackson-databind/issues/2434>

Thank you for the update. I hope Jackson users who run Jackson on OSGi
containers can help with this effort.

-+ Tatu +-

Steinar Bang

unread,
Oct 12, 2019, 4:22:47 PM10/12/19
to jacks...@googlegroups.com
>>>>> Tatu Saloranta <ta...@fasterxml.com>:

> Thank you for pointing that out was an oversight.
> I have to use mvn version:set plugin to update multi-module repos, but
> had forgotten to update base. Done now, pushed snapshot.

Thanks, now I have rebased all repos, except the following that are
still missing a 2.11 branch:

jackson-datatype-hibernate (well, I rebased this one on the newest master, but the version number was 2.10.1-SNAPSHOT and not 2.11.0-SNAPSHOT)
jackson-datatype-joda
jackson-datatype-json-org
jackson-datatype-jsr353
jackson-module-jsonSchema

Tatu Saloranta

unread,
Oct 16, 2019, 1:25:58 PM10/16/19
to Steinar Bang, jacks...@googlegroups.com
I added a note on issue too but here's the summary:

* joda, json-org, jsonSchema now have `2.11` branch
* jsonSchema module: planned to be deprecated after 2.x, so `master`
is actually for `2.11` now
* hibernate: may be deprecated afer 2.x, so `master` similarly not
building 3.0 but 2.11 (not firmly decided wrt deprecation: if new
owner(s) found, may be continue, just unsure at this point)

So: for jsonSchema and Hibernate modules, use `master`. For others
there should be 2.11. Please let me know if there are other gaps.

-+ Tatu +-

Steinar Bang

unread,
Nov 2, 2019, 5:50:17 PM11/2/19
to jacks...@googlegroups.com
>>>>> Tatu Saloranta <ta...@fasterxml.com>:

> I added a note on issue too but here's the summary:

> * joda, json-org, jsonSchema now have `2.11` branch
> * jsonSchema module: planned to be deprecated after 2.x, so `master`
> is actually for `2.11` now
> * hibernate: may be deprecated afer 2.x, so `master` similarly not
> building 3.0 but 2.11 (not firmly decided wrt deprecation: if new
> owner(s) found, may be continue, just unsure at this point)

Thanks! I saw the note on the issue as well.

I will put a note on the issue once all branches are rebased and sent to
the karaf maintainer for review.

> So: for jsonSchema and Hibernate modules, use `master`. For others
> there should be 2.11. Please let me know if there are other gaps.

ok, will do. I don't think there are (I have a checklist).

Re: the scala module mentioned in the note on the issue, see:
https://github.com/FasterXML/jackson-module-scala/issues/427#issuecomment-533833772

The module maintainer and myself decided not to do it, basically because
we don't know how to this with SBT.

Tatu Saloranta

unread,
Nov 4, 2019, 1:50:56 PM11/4/19
to Steinar Bang, jacks...@googlegroups.com
Makes sense. I can't publish scala module myself using sbt. Something
in set up is not working with my environment.
But perhaps if there is demand someone with more Scala knowledge can
help with that, eventually.

-+ Tatu +-

>
> --
> You received this message because you are subscribed to the Google Groups "jackson-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jackson-dev...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/864l08o3u0.fsf%40dod.no.
Reply all
Reply to author
Forward
0 new messages