[
https://issues.apache.org/jira/browse/AMQ-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon closed AMQ-7364.
---------------------------------------
Resolution: Duplicate
> Do not use jetty-all as dependency
> ----------------------------------
>
> Key: AMQ-7364
> URL: https://issues.apache.org/jira/browse/AMQ-7364
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.15.10
> Reporter: Joakim Erdfelt
> Priority: Major
>
> It seems that `activemq-http` is using the `jetty-all` artifact as a
> dependency from maven central.
> First noticed here.
> [https://stackoverflow.com/questions/59286348/spring-boot-2-2-activemq-jetty-conflict/59287124#59287124]
> `jetty-all` is not meant to be used as a dependency in a project.
> See https://www.eclipse.org/lists/jetty-users/msg06030.html
> It only exists as a command line tool for the documentation to educate folks
> about *basic* featureset of Jetty.
> It does not, and cannot, contain all of Jetty.
> A single artifact with everything that Jetty produces is actually impossible.
> Your use of `jetty-all` causes conflicts with classes across projects that
> use different features of Jetty and / or different libraries that also use
> Jetty properly. (such as wanting to use WebSocket, or HttpClient, or HTTP/2,
> or an alternate Session management, or any SSO library, or even spring)
> Use the individual artifacts, never the `jetty-all` artifact.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
