Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3039

Maven commands may fail for JBoss EAP XP Microprofile and JBoss EAP 7.4 in AirGap environment, as these devfiles use two separate users and containers

    XMLWordPrintable

Details

    • Hide
      • Authenticate at https://devspaces-openshift-workspaces.apps.crw-airgap-v10.crw-qe.com
      • Start a Java with JBoss EAP 7.4 devfile or Java JBoss EAP XP Microprofile devfile
      • settings.xml is auto-mounted into /home/user/.m2/
      • Build in `tools` container succeeds
      • Running any commands in other container fail, since the .m2 folder is not shared between the user home paths
      Show
      Authenticate at https://devspaces-openshift-workspaces.apps.crw-airgap-v10.crw-qe.com Start a Java with JBoss EAP 7.4 devfile or Java JBoss EAP XP Microprofile devfile settings.xml is auto-mounted into /home/user/.m2/ Build in `tools` container succeeds Running any commands in other container fail, since the .m2 folder is not shared between the user home paths
    • Workaround Exists
    • Hide

      Add .m2 volume to the eap containers, otherwise the package and run steps will fail

      Show
      Add .m2 volume to the eap containers, otherwise the package and run steps will fail
    • Hide
      = Maven commands failing for JBoss EAP

      Currently, Maven commands might fail for JBoss EAP XP MicroProfile and JBoss EAP 7.4 because these devfiles use two separate users and containers.

      .Workaround

      * In the dashboard, edit the devfile to add the `.m2` volume to the EAP container so that Maven commands can use the `.m2` folder.
      Show
      = Maven commands failing for JBoss EAP Currently, Maven commands might fail for JBoss EAP XP MicroProfile and JBoss EAP 7.4 because these devfiles use two separate users and containers. .Workaround * In the dashboard, edit the devfile to add the `.m2` volume to the EAP container so that Maven commands can use the `.m2` folder.
    • Documented as Known Issue

    Description

      These two devfiles have a separate `eap` container and separate `jboss` user used in those.
      The container cannot access `tools` container's /home/user/.m2

      There is a workaround of modifying a devfile and adding the volume mount manually to allow building to work in disconnected environment as well

      Attachments

        Issue Links

          Activity

            People

              vsvydenk Valerii Svydenko
              tdancs Tibor Dancs
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: