[AMQ-7364] Do not use jetty-all as dependency

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 5.15.10
• Assignee: Unassigned
• Reporter: Joakim Erdfelt
• Created: 11/Dec/19 13:50
• Updated: 30/Mar/22 13:26
• Resolved: 22/Jun/20 14:12

Description

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.

Issue Links

• causes: AMQ-8554 RESTful API: NoClassDefFoundError->ContinuationSupport
• duplicates: AMQ-7358 Use Jetty atomic jar instead of jetty-all uber jar