[ https://issues.apache.org/jira/browse/CONFIGURATION-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952712#comment-17952712 ]
Justin Bertram commented on CONFIGURATION-852: ---------------------------------------------- Hey, [~ggregory]. Thanks for responding so quickly! I _think_ your proposed solution would work. I can certainly try it out if you send a PR and let you know for sure. To be clear, I'm no expert with this stuff. :) > MANIFEST.MF in 2.12.0 now contains uses:="jakarta.servlet,javax. servlet" > ------------------------------------------------------------------------- > > Key: CONFIGURATION-852 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-852 > Project: Commons Configuration > Issue Type: Bug > Affects Versions: 2.12.0 > Reporter: Justin Bertram > Priority: Major > > We use commons-configuration2 in ActiveMQ Artemis which includes some OSGi > integration. Recently when [attempting to move from 2.11.0 to > 2.12.0|https://github.com/apache/activemq-artemis/pull/5663] an OSGi-related > test started failing, and it turns out that the culprit is that > {{Export-Package}} in {{MANIFEST.MF}} now contains: > {noformat} > uses:="jakarta.servlet,javax. servlet"{noformat} > I can update our configuration to account for this, but it's not clear to me > that this change was intentional given that the Maven dependencies for these > artifacts are marked as {{optional}}. > Does 2.12.0 really have a hard dependency on jakarta & javax servlet? -- This message was sent by Atlassian Jira (v8.20.10#820010)