Open victormunoz opened 8 years ago
I can confirm this behaviour. This is sad given how pretty the CLI is apart from that!
Apparently the .
and ..
elements in file paths are not resolved starting from the current working directory but from the DPF Manager installation directory. Here are some details (installation on Debian 9 with the current deb package for DPF Manager 3.5.1):
dpf-manager check .
does not scan the current working directory but the /opt/DPF Manager/app/
directory.dpf-manager check ..
does not scan the parent directory of the current working directory but the /opt/DPF Manager/
directory.dpf-manager check ../foo/
does not scan the directory ../foo/
but raises the error "ERROR - Error in input path ../foo/".dpf-manager check ~/foo/
works as expected!Yes. This is a known issue ...for a long time. It is produced by the tool we use to generate the exe. We have spend many hours looking into this, but there seems to be no way to configure the tool to change this behavior. Any help would be appreciated ;)
But, there is a possible workaround. Instead of running the executable, you can run directly the jar:
java -jar "/opt/DPF Manager/DPF Manager-jfx.jar" check .
When dpfmanager is run from CLI files passed with relative paths are not found