ScenarioManager CLI does not work for custom packages

The ScenarioManager CLI does not work for custom packages that are not in list of default packages when using a filepath to the scx file. Since the scx file knows which package it belongs to it should not be necessary to have the package in list of default packages.

The following error appears:

$ armarx scenario start . 
Profile: default
This executable is an application within the ArmarX framework.
==================================================================
 Starting an ArmarX Scenario
==================================================================
In order to start a Scenario pass either a path to an scx file or a Scenario name with a command. Example command:

  > armarx scenario command scxpath/scxname [package name] [-a application]

Help options:
  -h [ --help ]            Help option
  -c [ --command ] arg     What should be done: {
                            start, 
                            stop, 
                            kill, 
                            restart (kills by default), 
                            list (List all Scenario in Packages in 
                            ArmarX.DefaultPackages)
                           }
  -f [ --file ] arg (=.)   Path to the scx file (default: looks in current dir)
  -p [ --package ] arg     [optional] If the packages are included in your 
                           default config as ArmarX.DefaultPackages this can be
                           left empty
  -a [ --application ] arg [optional] Application out of the Scenario to 
                           execute the command with


Could not find any package for .. Please add an PackageName or Add the PackageName to your default config.