Strange Behavior with Commons-CLI

Hello,

I have a Java project with a Maven build in which a module uses commons-cli.  With version 1.9.0, the Maven build works correctly from the command line, but Eclipse and VS Code give an error that org.apache.commons.cli cannot be resolved to a module.  The strange thing is that if I drop back to version 1.6.0, the error disappears.  The command line build and the IDE build both work.  Any version after that produces the issue.  Eclipse lists the commons-cli jar in the Maven dependencies for any version used and they are physically present in ~/.m2.  Adding it manually to the module path does not help.

This is doubtless some problem buried in M2e, but I have not been able to resolve it for some time.  I'm wondering if you can provide any insight into what changed after 1.6.0 regarding the configuration as a Java 9+ module.  The error occurs when the system encounters 'requires transitive org.apache.commons.cli;' in module-info.java.

The project is fully modularized and built with Java 21 and Maven 3.9+.

Thanks in advance,
Frank