On Tue, Aug 27, 2019 at 8:44 PM Marcos Passos <marcospassos....@gmail.com> wrote: > > Hi folks! > > I've opened a PR that introduces the possibility of declaring modules > dependencies to ensure the object mapper will register the required module as > well. > > In our case, we've several modules that depend on the Jdk8Module. We also > have modules that depend on other modules, e.g.: > > Module A depends on Jdk8Module > Module B depends on Module A and Jdk8Module > Module C depends on Module B and Jdk8Module > > > When you split the serialization modules into fine-grained modules, it's much > easier to declare the dependencies at the module level rather than requiring > the dependency every time you have to use it. > > Please, feel free to leave your comments about the proposal.
I am hoping to hear from anyone interested, who has had challenges in maintaining (custom) modules; or who otherwise has opinions on this. Part of the reason I am eager to hear about this relatively soon is that I am hoping to close work on 2.10 -- 2.10.0.pr2 should be released within next 4-5 days, and although this is not a deadline for all work, additions beyond pr2 will get less testing and may face more scrutiny. Proposed change itself is quite safe but assuming this seems like a feature of interest to others I would like to get API somewhat right. -+ 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/CAL4a10hK18ZtjEmaSJuPHyp7VHNm_62z0oUgoz3tnWfzO35LeA%40mail.gmail.com.
