[
https://issues.apache.org/jira/browse/AMQ-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated AMQ-8569:
--------------------------------
Description:
The activemq-client module has a 'provided' dependency on xstream, meaning
users do not get that dependency passed on, they need their own dependency on
it. The osgi details in the activemq-client manifest however dont list it as
optional, so it is required there. This requirement perhaps hasnt been
effective in many prior releases though (e.g see 5.15.15, 5.16.0 and 5.16.1 for
example) as the manifest is clearly truncated mid-declaration in earlier
releases and may have omitted it depending on ordering etc.
The details in the activemq-osgi manifest do list xstream as optional. It seems
like activemq-client should also.
was:
The activemq-client module has a 'provided' dependency on xstream, meaning
users do not get that dependency passed on. The osgi details in the
activemq-client manifest however dont list it as optional, so it is required
there. This requirement perhaps hasnt been effective in many prior releases
though (e.g see 5.15.15, 5.16.0 and 5.16.1 for example) as the manifest is
clearly truncated mid-declaration in earlier releases and may have omitted it
depending on ordering etc.
The details in the activemq-osgi manifest do list xstream as optional. It seems
like activemq-client should also.
> mismatch in activemq-client osgi and pom dependency requirements
> ----------------------------------------------------------------
>
> Key: AMQ-8569
> URL: https://issues.apache.org/jira/browse/AMQ-8569
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.17.0
> Reporter: Robbie Gemmell
> Priority: Major
> Fix For: 5.17.1
>
>
> The activemq-client module has a 'provided' dependency on xstream, meaning
> users do not get that dependency passed on, they need their own dependency on
> it. The osgi details in the activemq-client manifest however dont list it as
> optional, so it is required there. This requirement perhaps hasnt been
> effective in many prior releases though (e.g see 5.15.15, 5.16.0 and 5.16.1
> for example) as the manifest is clearly truncated mid-declaration in earlier
> releases and may have omitted it depending on ordering etc.
> The details in the activemq-osgi manifest do list xstream as optional. It
> seems like activemq-client should also.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
