Thanks for the quick response, the module_info.class is stored in a common location when we create a patch for cutomers with all 3 jars in the same "jackson-updated-security patch", here is an example error from our system:
ERROR: Different size module-info.class duplicated in archives: fnd/java/3rdparty/stdalone/jackson_annotations.zip (120.0.12020000.7), fnd/java/3rdparty/stdalone/jackson_databind.zip (120.0.12020000.7), fnd/java/3rdparty/stdalone/jackson_core.zip (120.0.12020000.7) java/3rdparty/stdalone/jackson_core.zip One option that we re thinking is maybe create 3 separate patches, but that will cause an error when the patches are applied in the same customer location. On Tuesday, January 28, 2020 at 11:03:53 AM UTC-8, Ron Karim (Oracle Corp.) wrote: > > As we are upgrading jackson modules to version 2.10.2, we are using > jackson_core, jackson_databind and jackson_annotations (all versions > 2.10.2), > Each of these jars have a module_info.class that seems to be different in > each jar. Hence we cannot use these 3 jars in our systems. > > Should we be using the same 2.10.2 version for jackson_core and ja > kson_annotations too ? Along with the jackson_databind 2.10.2 ? > > Or is there another resolution to dealiing with the module_info.class in > each of these jars ? > > Appreciate your help. > > -- You received this message because you are subscribed to the Google Groups "jackson-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to jackson-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/80a3fbd0-41aa-470d-922b-e8d019c0efff%40googlegroups.com.
