Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19463 CY2024Q3 Quickstarts Enhancements
  3. WFLY-19810

Quickstarts should never deploy as ROOT.war

XMLWordPrintable

          [WFLY-19810] Quickstarts should never deploy as ROOT.war

          Jeff Mesnil added a comment -

          technically, there should be no issues with that change.

          Jeff Mesnil added a comment - technically, there should be no issues with that change.

          Eduardo Martins added a comment -

          jmesnil1@redhat.com Yes, the README instructions will need an update, most will be done in a shared-docs content, yet some (eg todo-backend) may need an additional update, but wrt deployment (s2i, bootable jar) it will work? I mean users are not forced to deploy as root, right?

          Eduardo Martins added a comment - jmesnil1@redhat.com Yes, the README instructions will need an update, most will be done in a shared-docs content, yet some (eg todo-backend) may need an additional update, but wrt deployment (s2i, bootable jar) it will work? I mean users are not forced to deploy as root, right?

          Jeff Mesnil added a comment -

          There might be an UX issue associated with that change.

          If a user starts from the OpenShift route URL, they will have a 404 and will need to append the deployment path to access the application endpoints.

          Jeff Mesnil added a comment - There might be an UX issue associated with that change. If a user starts from the OpenShift route URL, they will have a 404 and will need to append the deployment path to access the application endpoints.

            emartins@redhat.com Eduardo Martins
            emartins@redhat.com Eduardo Martins
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: