Re: Strange Behavior with Commons-CLI

Yes, the lilnk is helpful. Moditech seems to think it is only a problem when compiling within Eclipse, but my experience is that anything that uses M2E will be affected. That's a larger pool. F. > On Jun 24, 2025, at 04:58, Gary Gregory wrote: > > Thanks for the link, hopefully we can get so

Re: Strange Behavior with Commons-CLI

Thanks for the link, hopefully we can get some feedback soon. Gary On Tue, Jun 24, 2025, 07:31 Ruby Paasche wrote: > Yes, seems to be a Problem in 1.2.x, downgrade to 1.1.x seems to be the > Workaround: > https://github.com/moditect/moditect/issues/254 > > > > > Am Di., 24. Juni 2025 um 13:02

Re: Strange Behavior with Commons-CLI

Hi, see also https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2495#issuecomment-2254297050 The problem is that the commons-cli jar misses directory entries for 'versions/9/' under 'META-INF'. The module-info.class was somehow added without them. The eclipse module name resolver used f

Re: Strange Behavior with Commons-CLI

Hi, see also https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2495#issuecomment-2254297050 The problem is that the commons-cli jar misses directory entries for 'versions/9/' under 'META-INF'. The module-info.class was somehow added without them. The eclipse module name resolver used f

Re: Strange Behavior with Commons-CLI

Yes, seems to be a Problem in 1.2.x, downgrade to 1.1.x seems to be the Workaround: https://github.com/moditect/moditect/issues/254 Am Di., 24. Juni 2025 um 13:02 Uhr schrieb Gary Gregory < garydgreg...@gmail.com>: > Hello Kolja, > > Thank you for the clarification. Would you say this is a bug

Re: Strange Behavior with Commons-CLI

Hello Kolja, Thank you for the clarification. Would you say this is a bug in the Moditect Maven plugin? Because it doesn't follow the JAR specification? Ty, Gary On Tue, Jun 24, 2025, 06:47 Kolja wrote: > Hi, > > see also > > https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2495#issuecom

Re: Strange Behavior with Commons-CLI

Hopefully you can create an m2e ticket and post a link to it here. Ty, Gary On Sun, Jun 22, 2025, 18:50 Frank wrote: > BTW, Just opened the project in IntelliJ. Maven POM is unchanged except > to up the Commons CLI version to 1.9.0. No problems with module detection. > F. > > > On Jun 22, 2

Re: Strange Behavior with Commons-CLI

BTW, Just opened the project in IntelliJ. Maven POM is unchanged except to up the Commons CLI version to 1.9.0. No problems with module detection. F. > On Jun 22, 2025, at 14:25, Gary Gregory wrote: > > On Sun, Jun 22, 2025 at 5:01 PM Frank > wrote:

Re: Strange Behavior with Commons-CLI

On Sun, Jun 22, 2025 at 5:01 PM Frank wrote: > > I added your snapshot repo, changed my pom.xml and verified in Eclipse that I > was truly using commons-cli-1.10.0-SNAPSHOT.jar. Unfortunately, I still see > the same problem. org.apache.commons.cli is not recognized as a module. I > have no t

Re: Strange Behavior with Commons-CLI

Ah, certainly not. If you had changed the module name, my command line Maven build wouldn't work. For your earlier question, the command line build has always worked. I verified again just today that it works with 1.9.0. F. > On Jun 22, 2025, at 14:00, Frank wrote: > > I added your snapshot

Re: Strange Behavior with Commons-CLI

I added your snapshot repo, changed my pom.xml and verified in Eclipse that I was truly using commons-cli-1.10.0-SNAPSHOT.jar. Unfortunately, I still see the same problem. org.apache.commons.cli is not recognized as a module. I have no trouble believing that M2E is the culprit. I've had to p

Re: Strange Behavior with Commons-CLI

Hm I think our OSGi tests don't run since we ported to JUnit 5. Gary On Sun, Jun 22, 2025 at 3:26 PM Gary Gregory wrote: > > Hello Frank, > > Are you saying that no matter what version of Commons CLI you use and > then build from the command line with Maven, all is well? > > If the above is true

Re: Strange Behavior with Commons-CLI

Hello Frank, Are you saying that no matter what version of Commons CLI you use and then build from the command line with Maven, all is well? If the above is true, then this suggests one of two things: Something is wrong with M2E or something is wrong with the OSGi metadata in Commons CLI, I don'

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