Lack of relocated classes information in IDE environment

I'm using maven-shade-plugin in my multi module Maven Java Project.

root
|-- module-a
|-- |-- pom.xml
|-- module-b
|-- |-- pom.xml
pom.xml

module-b depents on module-a.

module-a depents on the kafka-client lib (third-party lib), and in the pom of module-a I add this to shade kafka-client lib into the final module-a Jar so that no kafka-client dependency will be passed to module-b:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-shade-plugin</artifactId>
    <version>3.6.0</version>
    <executions>
        <execution>
            <phase>package</phase>
            <goals>
                <goal>shade</goal>
            </goals>
            <configuration>
                ...
                <!-- relocate package name -->
                <relocations>
                    <relocation>
                        <pattern>org.apache.kafka</pattern>
                        <shadedPattern>com.a.b.c.org.apache.kafka</shadedPattern>
                    </relocation>
                </relocations>
                ...
            </configuration>
        </execution>
    </executions>
</plugin>

module-b depents on module-a so it will import the relocated classes in kafka-client which is contained in module-a Jar.

But when I try to import the project into VSCode I got error "The import com.a.b.c cannot be resolved Java(268435846)" in module-b like:

I think maybe vscode is not including the shaded jar into project environment?

No offense, but IntelliJIDEA handled like this without error alert, project seems all good after importing:

Maybe we can take it into consideration?

Thank you very much.

VS Code version: Code 1.101.2 (Universal) (2901c5ac6db8a986a5666c3af51ff804d05af0d4, 2025-06-24T20:27:15.391Z)
OS version: Darwin arm64 24.5.0
Modes:

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
2e7ec940:31000449
cppperfnew:31000557
dwnewjupyter:31046869
nativeloc1:31344060
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
4gafe986:31271826
c7cif404:31314491
pythonpulldiag:31343502
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
9d2cg352:31339597
0g0a1943:31341127
d7aab740:31338110
usemarketplace:31343026
nesew2to5:31336538
agentclaude:31335815
mytestcf:31335658
nes-diff-11:31337487
6abeh943:31336334
yijiwantestdri0626-t:31336930
4gdec884:31342391

Commencez par reproduire le projet Maven multi-module dans VS Code et examinez comment l’environnement Java résout la dépendance de module-b envers module-a et ses classes shaded de kafka-client. Comparez cela avec la configuration fonctionnelle d’IntelliJ IDEA ; le travail est terminé lorsque les imports sous com.a.b.c sont résolus sans diagnostics Java.