[
https://issues.apache.org/jira/browse/CONFIGURATION-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17826839#comment-17826839
]
Bob Marinier commented on CONFIGURATION-839:
--------------------------------------------
Yes, I'm using maven. The output of maven -version is:
{code:java}
Maven home: C:\apache-maven-3.9.5
Java version: 17.0.10, vendor: Eclipse Adoptium, runtime: C:\Program
Files\Eclipse Adoptium\jdk-17.0.10.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"{code}
The same issue arises in my gitlab pipeline, which is running on linux (it was
using the docker container maven:3.9-eclipse-temurin-11 when I reported this
issue, but I just changed it to maven:3.9-eclipse-temurin-17).
I will see if I can make a simple reproducer.
> Commons configuration 2.10.0 fails with module error
> ----------------------------------------------------
>
> Key: CONFIGURATION-839
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-839
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 2.10.0
> Reporter: Bob Marinier
> Priority: Major
>
> My system was using apache configuration 2.9.0 without issue. After upgrading
> to 2.10.0, I get this error at startup:
> {code:java}
> [ERROR] Error occurred during initialization of boot layer
> [ERROR] java.lang.module.FindException: Module servlet.api not found,
> required by org.apache.commons.configuration2{code}
> I am running on Java 17 on Windows 11. Other than this dependency version
> change, nothing else about my system has changed. For now I'll go back to
> 2.9.0, but I'm worried about being able to upgrade in the future.
> My specific java version is:
> {code:java}
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment Temurin-17.0.10+7 (build 17.0.10+7)
> OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (build 17.0.10+7, mixed mode,
> sharing){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
