Description
I created a Mapstore project with the project generator script (using Mapstore as a submodule). When I try to customize the path to the print configuration using the option -Dmapfish-print-config=/path/to/config.yaml
npm run be:start -- -Dmapfish-print-config="path/to/print/config.yaml"
The option is ignored and the default path is used instead.
How to reproduce
- Create a Mapstore project with the generator
- Create a custom
config.yaml file
- Pass the path to this custom config file to the
npm run be:start command:
npm run be:start -- -Dmapfish-print-config="path/to/print/config.yaml"
Expected Result
The custom configuration file is used by the print module.
Current Result
The default configuration file is used by the print module.
Browser info
(use this site: https://www.whatsmybrowser.org/ for non expert users)
| Browser Affected |
Version |
| Internet Explorer |
|
| Edge |
|
| Chrome |
|
| Firefox |
|
| Safari |
|
Other useful information
Description
I created a Mapstore project with the project generator script (using Mapstore as a submodule). When I try to customize the path to the print configuration using the option
-Dmapfish-print-config=/path/to/config.yamlnpm run be:start -- -Dmapfish-print-config="path/to/print/config.yaml"The option is ignored and the default path is used instead.
How to reproduce
config.yamlfilenpm run be:startcommand:npm run be:start -- -Dmapfish-print-config="path/to/print/config.yaml"Expected Result
The custom configuration file is used by the print module.
Current Result
The default configuration file is used by the print module.
Browser info
(use this site: https://www.whatsmybrowser.org/ for non expert users)Other useful information