[
https://issues.apache.org/jira/browse/QPID-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4645:
---------------------------------
Description:
The broker module does not depend on the broker-plugins at compile time, and so
its generated pom currently doesn't mention them at all. It does however depend
on the management plugins at runtime. We should add the broker plugins as
runtime dependencies in the broker pom, with the optional bdbstore modules
listed as optional as optional dependencies.
Most of the broker-plugins use 'provided' scope for the broker dependencies for
historical reasons relating to their previous osgification (shipping certain
deps at the broker level and exporting them, plus needing to place them in a
completely different location from the core broker jars). The optional bdbstore
module does not, but it would be useful if it aligned with the others and
indeed would be good to ensure the optional [non-Apache Licence] BDB JE
dependency must be added explicitly in the users pom in addition to the
conscious choice to explicitly add the bdbstore module itself in general.
was:
The broker module does not strictly depend on the broker-plugins, and so its
generated pom currently doesn't mention them at all. It would be useful for
users however if we drew attention to and made gathering dependency info for
the plugins easier by simply adding them as optional dependencies in the broker
pom.
Most of thehe broker-plugins use 'provided' scope for the broker dependencies
for historical reasons relating to their previous osgification (shipping
certain deps at the broker level and exporting them, plus needing to place them
in a completely different location from the core broker jars). The optional
bdbstore module does not, so it would be useful if it aligned with the others
and is indeed would be good to ensure the optional JE dependency must be added
explicitly in the user pom in addition to the conscious choice to explicitly
add the bdbstore module itself in general.
> [Java broker] add plugins as runtime dependencies in the broker pom, and make
> the optional bdbstore module dep scopes in line with other plugins
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4645
> URL: https://issues.apache.org/jira/browse/QPID-4645
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.21
>
>
> The broker module does not depend on the broker-plugins at compile time, and
> so its generated pom currently doesn't mention them at all. It does however
> depend on the management plugins at runtime. We should add the broker plugins
> as runtime dependencies in the broker pom, with the optional bdbstore modules
> listed as optional as optional dependencies.
> Most of the broker-plugins use 'provided' scope for the broker dependencies
> for historical reasons relating to their previous osgification (shipping
> certain deps at the broker level and exporting them, plus needing to place
> them in a completely different location from the core broker jars). The
> optional bdbstore module does not, but it would be useful if it aligned with
> the others and indeed would be good to ensure the optional [non-Apache
> Licence] BDB JE dependency must be added explicitly in the users pom in
> addition to the conscious choice to explicitly add the bdbstore module itself
> in general.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
