Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-15908

Upgrade javax.websocket-api to jakarta.websocket-api

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 16.0.0
    • None
    • None

    Description

      Found in CMS-15882, related to CMS-15637 (Jakarta):

      community/services-autoreload/pom.xml has:

          
      <properties>
         <javax.websocket-api.version>1.1</javax.websocket-api.version>
       </properties>
        
          <dependency>
            <groupId>javax.websocket</groupId>
            <artifactId>javax.websocket-api</artifactId>
            <version>${javax.websocket-api.version}</version>
            <scope>provided</scope>
          </dependency>
      

      This artifact moved to jakarta.websocket-api, see https://mvnrepository.com/artifact/javax.websocket/javax.websocket-api

      Unknown if anything is broken, websockets are used in local development environment to push changed webfiles to the browser. But assuming package renames are in order, javax.websocket to jakarta.websocket

      [edit] Indeed Live Reloading during local development, as described here, is broken because Tomcat 10 provides jakarta.websocket-api.jar and code base still contains javax.websocket.

      Attachments

        Issue Links

          Activity

            People

              jhoffman Jeroen Hoffman
              jhoffman Jeroen Hoffman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: