Duplicates between dropwizard 2.0.2 and jooq 3.13.1

[psouquet]

trafficstars

Hi again ! Importing dropwizard-jooq:2.0.2-0 along with dropwizard-core:2.0.2 creates duplicated classes/ressources issues at compilation. Some equal some different. Classes/ressources are in jakarta.xml.bind-api:2.3.2 / jakarta.activation-api:1.2.1 and jaxb-api:2.3.1 / javax.activation-api:1.2.0.

• dropwizard-core:2.0.2, dropwizard-testing:2.0.2 and dropwizard-migrations:2.0.2 all transitively depends on jakarta.xml.bind-api:2.3.2 > jakarta.activation-api:1.2.1.

• dropwizard-jooq:2.0.2-0 depends on jooq:3.13.1 > jaxb-api:2.3.1 > javax.activation-api:1.2.0.

I tried to work around that by excluding jaxb-api from dropwizard-jooq in maven, but I don't know if that is viable as I encountered another (and unrelated) issue that will need an external fix.

I don't know what would be a good fix for you on this issue, because it seems that dropwizard added that runtime dependency in dw 2.0.1 (it was not in 2.0.0) straight at jakarta.xml.bind-api:2.3.2. And jooq 3.13.1 is the latest available for now. I'm afraid that, considering these are different artifacts packaging same classes, even aligning versions would still bring duplicates (though they should be equals)...

What do you think ?

[benjamin-bader]

Uh oh, good catch. Off the top of my head, I can't say whether it's safe to exclude jaxb-api from jooq. If you get it working that way, let me know and I'll try to incorporate your fix in this project!

[psouquet]

Ok, I'll let you know. We might have to wait for a bit because another integration dependency is blocking my update and nothing works for now with dropwizard 2...

Anyway, thanks for your response !

[benjamin-bader]

Hi there. Any update here? Is this still an issue for you?

[psouquet]

The other issue was not resolved and is still blocking for me... I'll let you know when I take another shot at updating dropwizard.