Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-7364

Do not use jetty-all as dependency

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 5.15.10
    • None
    • None
    • None

    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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              joakime Joakim Erdfelt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: