[
https://issues.apache.org/jira/browse/CONFIGURATION-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated CONFIGURATION-852:
-----------------------------------------
Summary: OSGi Import-Package in 2.12.0 now requires jakarta.servlet (was:
MANIFEST.MF in 2.12.0 now contains uses:="jakarta.servlet,javax. servlet")
> OSGi Import-Package in 2.12.0 now requires jakarta.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
> Fix For: 2.12.1
>
>
> 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)
