Eclipse having issues due`module-info` class "lost" on 2.18.0 jars

[bwzhang2011]

Describe the bug

module info lost during the release since jackson-databind 2.18.0 version while correct in early version released like 2.17.2. notice that 2.17.2 is correct for databind core and annotation package. I recommend new deployed version to be released which could help the upgration of jacskon

Version Information

2.18.0

Reproduction

Not given

Expected behavior

no error while import module class support

Additional context

None

[pjfanning]

Can you give more details? The issue is in jackson-databind 2.18.0 jar and only that jar?

I downloaded jackson-databind 2.18.0 jar and it has:

 1496  09-26-2024 18:56   META-INF/versions/9/module-info.class

[AndreasWBartels]

compile with maven 3.9.5 (and newer) with jdk21 works (openjdk and temurin)

eclipse does not seem to be able to handle the multi version jar which it can with 2.17.2.

tested with eclipse 2024-03 and 2024-09

there is a similar issue on eclipse.jdt.core for gson

[GedMarc]

That is 100% an eclipse problem,

Also found animal sniffer doesn't like compiles into alternative versions, e.g. jdk11 compiling into versions/17 , throws a java error -
Same issue, the location of /9 is correct as well,
This is internal to eclipse.

[pjfanning]

jackson-core is a Multi-Release jar - not jackson-databind

I agree with @GedMarc that this does not appear to be an issue in jackson-core/jackson-databind and that issue is in tooling that users are using. @bwzhang2011 provided very little detail on what their issue is.

[cowtowncoder]

Not sure if this might be related to a jackson-core fixed issue FasterXML/jackson-core#1340.

Either way description is too incomplete to be actionable; closing. May be re-opened or re-filed with more information; in particular showing how to reproduce the issue.

EDIT: as per @GedMarc that issue appears unrelated to whatever issue was here.

[AndreasWBartels]

This is a moditect issue moditect/moditect#254

Which unfortunately makes it a jackson issue, because you should either downgrade or upgrade as soon as the issue for moditect is fixed.

[pjfanning]

moditect/moditect@5d63f7b seems to be in every release since 1.2.0.Final so maybe the best course of action is to downgrade to moditect 1.1.0 in all Jackson repos - 2.18 branches.

https://mvnrepository.com/artifact/org.moditect/moditect/1.1.0

[pjfanning]

@AndreasWBartels Thanks for the analysis. Moditect is a pretty widely used tool and the commit that you highlight appears to have been in 3 releases of Moditect in the last 6 months. The internet is not ablaze with people complaining about broken jars. My vote would be to use an old version of Moditect until a fix is made - but that there is no reason to rush out a Jackson release.

Users can stick to older Jackson releases if they think they might be affected by this.

[cowtowncoder]

Uggggh. Moditect downgrade is tricky since if I recall it comes via parent poms. And verification of newer versions, once available, seems difficult.

But if we have to, we have to.

[GedMarc]

I'll update the jdk11 compat test to 2.18, should be able to add a test case there,
Will check on moditect as well