Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
7.17.2, 7.18.0-alpha2
-
None
Description
Environment:
- 7.18.0-alpha2-ee
- Microsoft Windows 10 Pro (Build 19044)
Description:
When trying to launch Camunda Run (via start.bat) from a folder with spaces in its path (e.g. C:\My Folder) the application doesn't successfully start. Instead the detached CMD window just flashes briefly. When running the command "run.bat start" manually from inside the "\internal" folder, the following error message is printed:
C:\My Folder\internal>run.bat start Setting JAVA property to "C:\Program Files\Eclipse Adoptium\jdk-17.0.3.7-hotspot\\bin\java" REST API enabled WebApps enabled Swagger UI enabled Invoice Example included - needs to be enabled in application configuration as well classpath: C:\My Folder\internal\webapps,C:\My Folder\internal\rest,C:\My Folder\internal\swaggerui,C:\My Folder\internal\example,C:\My Folder\internal\..\configuration\userlib,C:\My Folder\internal\..\configuration\keystore Fehler: Hauptklasse Folder\internal\..\configuration.resources konnte nicht gefunden oder geladen werden Ursache: java.lang.ClassNotFoundException: Folder\internal\//\configuration/resources
Steps to reproduce:
- Extract a fresh copy of Camunda Run into a folder with spaces in its path (e.g. C:\My Folder)
- Try to launch Camunda Run via start.bat.
Observed Behavior:
The application doesn't successfully launch. Instead the CMD window just briefly flashes.
Expected behavior:
Camunda Run should launch without any errors from a folder with spaces in its path.
Solution Ideas:
Wrapping the argument details (%DEPLOYMENTDIR) of -Dcamunda.deploymentDir in quotation marks (lines 131 + 134) seems to fix the problem. Example:
call %JAVA% -Dloader.path="%classPath%" -Dcamunda.deploymentDir="%DEPLOYMENTDIR%" %JAVA_OPTS% -jar "%BASEDIR%camunda-bpm-run-core.jar" --spring.config.location=file:"%configuration%"