To decide what kind of issue this is, the developers would need:
- A small, self-contained program to reproduce.
- Alternatively, source code and some reproducible build.
The exception happens inside JBoss' Indexer.java, but it's unclear what
it's trying to do, why it was called, so nobody can diagnose whether the
bug is in Guava or in the caller. The issue here is that there are no
Guava line numbers (i.e. it's using a non-debug build), so somebody with
enough time would have to look into Guava and has has a mere 50-50
chance to actually see the problem (assuming Guava and application are
equally likely).
From the looks of the original message, it's likely a PEBKAC - putting
a JAR file into C:\ means that's a completely unprofessional
environment, so I'd probably ignore this entirely if I were on the Guava
team.
IOW I'd recommend posting your own message, with a Main.java and
build.gradle to make the build reproducible (pom.xml would likely work,
too).
HTH
Jo