Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-17679

Fix NuxeoLauncher.start() on paths with space on windows

    Details

    • Tags:
    • Backlog priority:
      800
    • Sprint:
      DevOps Sprint 11, nxSL Sprint 9.1.5, nxSL Sprint 9.1.6, nxSL Sprint 9.1.7
    • Story Points:
      5

      Description

      It seems that a space in the path to Nuxeo home leads to an NPE in some conditions (Win OS?) on org.nuxeo.launcher.NuxeoLauncher.start(boolean).

      Raised under Windows on 6.0-HF17:

      Exception in thread "NuxeoLauncherGUITask-7" java.lang.NullPointerException
              at org.nuxeo.launcher.NuxeoLauncher.start(NuxeoLauncher.java:614)
              at org.nuxeo.launcher.NuxeoLauncher.doStart(NuxeoLauncher.java:1392)
              at org.nuxeo.launcher.NuxeoLauncher.doStartAndWait(NuxeoLauncher.java:12
      27)
              at org.nuxeo.launcher.NuxeoLauncher.doStartAndWait(NuxeoLauncher.java:11
      85)
              at org.nuxeo.launcher.gui.NuxeoLauncherGUI$5.run(NuxeoLauncherGUI.java:2
      77)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
      java:1145)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
      .java:615)
              at java.lang.Thread.run(Thread.java:745)

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days
                2d

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.