Invalid package reference to "java.lang.foreign" from `com.fasterxml.jackson.core:jackson-core` (from `FastDoubleParser`) [Android]

[baywet]

Adding v2.18.3 in an android project leads to the following error message when running gradle build.

Error: Invalid package reference in com.fasterxml.jackson.core:jackson-core; not included in Android: java.lang.foreign. Referenced from com.fasterxml.jackson.core.internal.shaded.fdp.v2_18_3.FastDoubleSwar

No workaround is known, besides downgrading the dependency.

More context:

• https://github.com/microsoft/kiota-java/actions/runs/15538363819/job/43742832455?pr=1932
• chore(deps): bump com.azure:azure-core from 1.55.3 to 1.55.4 in /components/authentication/azure microsoft/kiota-java#1932
• Update Jackson dependencies to 2.18.3 Azure/azure-sdk-for-java#44968

[cowtowncoder]

I don't know what could be done here, although this seems odd: FastDoubleParser (https://mvnrepository.com/artifact/ch.randelshofer/fastdoubleparser/1.0.90) is included as shaded component, and it has not dependencies of its own.

So is there any chance Android SDK tooling might have an issue to fix? (or maybe this works with certain version of ASDK).

Also worth checking if Jackson 2.19.0 is any different in this regard (none of changes seems relevant but just in case).

[cowtowncoder]

Ok. Perhaps this is due to FastDoubleParser version upgrade included in 2.18.1. If so, 2.18.0 might actually work, as it still depends on 1.0.1 instead of 1.0.90

But I really hope this is not it because... that'd be difficult thing to reconcile wrt compatibility.

/cc @pjfanning .

[pjfanning]

FastDoubleSwar is multi-release jar class. That is, a class where the jar has different versions of the class targeted at different Java versions. These versioned classes appear in META-INF/versions/11 where 11 is the Java version.
https://openjdk.org/jeps/238

java.lang.foreign is pretty new so FastDoubleSwar would only be set up to use this package for the latest Java versions (eg Java 21).

Whatever Android set up is being use by @baywet seems not to be able to handle JEP 238.

Is this not Android's problem? The JEP is not new. If they want to use Java classes, shouldn't they be up to date with the JEPs?

[baywet]

@cowtowncoder thanks for the quick reply!

Here is the full repo (in android studio):

1. create a new project (empty activity, api level 26)

2. add the following dependencies in /app/build.gradle (.kts if kotlin was selected)

   implementation("com.fasterxml.jackson.core:jackson-core:2.19.0")

3. Add the following option above the dependencies section

   lint {
        checkAllWarnings = true
    }

4. run gradle build

[cowtowncoder]

Looks like java.lang.foreign was officially added in JDK 22 (although preview in 21)

So one work-around could be to just drop JDK-specific optimized classes under META-INF/versions/22/ in jackson-core jar.
Or perhaps both 21 and 22 .

This assuming nothing else works: ideally of course Android tooling would ignore classes for JDKs they are not compatible with.

[cowtowncoder]

Thank you @baywet . I don't have Android dev setup myself, but this should be helpful for others (or possibly myself eventually).

[pjfanning]

I'm not against blocking the Java 22 classes from jackson-core. We've had build time filtering of the FastDoubleParser versioned classes before.

[baywet]

After iterating over all the recent versions I can confirm that 2.18.0 is the FIRST version this starts failing. And that 2.19.0 is also failing.

[cowtowncoder]

@baywet Interesting. If so, maybe it's FDP 1.0.0 to 1.0.1 that triggered the issue, not 1.0.1 -> 1.0.90.
In that case, 2.17.3 would have same issue. If so, we'd want to patch 2.17 as well as 2.18.

[pjfanning]

@cowtowncoder the Java 21 version of FastDoubleSwar does not use java.lang.foreign.

[baywet]

@pjfanning thanks for joining this thread. Although I'm far from a Java experienced dev (or Android for that matter), from reading the documentation I agree that any class making use of Foreign should only be "present" from java 19 and up (in preview), which seems to have been made stable by version 22.

These versioned classes appear in META-INF/versions/11 where 11 is the Java version

Consequently this seems incorrect and should be corrected. Ideally to 22.

[cowtowncoder]

One reason it'd be important to resolve this for 2.18 is that as per JSTEP-13 (LTS versions for Jackson):

https://github.com/FasterXML/jackson-future-ideas/wiki/JSTEP-13

2.18 is planned to be the first such version (for various reasons). So while patching 2.17 would be good, 2.18 is more of essential.