Allow jackson-module-jaxb-annotations to tolerate 2.2,3 in Import-Package #235
Conversation
| <version>${version.jaxb.impl}</version> | ||
| <groupId>javax.xml.bind</groupId> | ||
| <artifactId>jaxb-api</artifactId> | ||
| <version>2.2.12</version> |
There was a problem hiding this comment.
Shouldn't this instead change version.jaxb.impl property?
|
Hmmh. I am really uncomfortable with this change -- I know JAXB/Jakarta upgrade has been a Royal Mess, and I am not sure this helps in general. It seems to me that there are TWO overlapping distinct packages (as in, different Maven coordinates) that nonetheless both provide same classes: one with And in particular making change in a patch of 2.16, if breaking, would be very unfortunate. Especially as we are downgrading a dependency. Is it not possible to add local overrides on package depending on JAXB annotations module? @GedMarc WDYT? |
Resolves #233
I removed the Jakarta import, from the comment
Despite groupId, this is "old" JAXB, not Jakarta (3.x is real Jakarta one)it sounds like this should be OK. The end result in the MANIFEST.MF was the same as when I just added the jaxb-api dependency above it.