Warnings when compiling types that rely on @JsonAdapter from another compilation unit

[benalexau]

Issue #434 fixed a bug where a type relies on a @JsonAdapter in a different compilation unit, but I have just noticed we still see warnings during compilation.

Steps to easily reproduce using an attachment provided in #434:

wget https://github.com/user-attachments/files/22695378/issue-external.zip
unzip issue-external.zip
cd issue
sed -i 's/3.8-RC1/3.8-RC2/' pom.xml
mvn clean test

The warnings are shown below:

[INFO] --- compiler:3.14.1:testCompile (default-testCompile) @ avaje-jsonb-issue ---
[INFO] Recompiling the module because of changed dependency.
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
[INFO] Compiling 2 source files with javac [debug target 21] to target/test-classes
[WARNING] location of system modules is not set in conjunction with -source 21
  not setting the location of system modules may lead to class files that cannot run on JDK 21
    --release 21 is recommended instead of -source 21 -target 21 because it sets the location of system modules automatically
[WARNING] com.github.f4b6a3.ulid.Ulid, non public field msb with no matching setter or constructor?
[WARNING] com.github.f4b6a3.ulid.Ulid, non public field lsb with no matching setter or constructor?
[INFO] com.github.f4b6a3.ulid.Ulid, non accessible field msb
[INFO] com.github.f4b6a3.ulid.Ulid, non accessible field lsb
[INFO] Skipped writing JsonAdapter for com.github.f4b6a3.ulid.Ulid due to non accessible fields
[WARNING] File for type 'testing.jsonb.TestJsonComponent' created in the last round will not be subject to annotation processing.

The test does pass. This issue is purely about the warnings.

[SentryMan]

Hmm