When one runs the plugin and installs the resulting debian package, I am aware that it replaces the mustache variables in the config yaml file and the resulting file is then stored in /etc/application-name.yml at the time of the package installation.
However this doesn't have an option to produce another config yaml file to run normally in commandline "java -jar target/application.jar server config.yml". So as expected when one tries to run their application on command-line, the mustache variables in the original config yaml file cause the following error :
Exception in thread "main" com.fasterxml.jackson.core.JsonParseException: Expected a field name (Scalar value in YAML), got this instead: <com.fasterxml.jackson.dataformat.yaml.snakeyaml.events.MappingStartEvent(anchor=null, tag=null, implicit=true)>
at [Source: java.io.FileInputStream@6f10d5b6; line: 5, column: 12]
Is there a way or options within the plugin to have multiple config yaml files produced (instead of the one which eventually ends in the /etc/application-name.yml) as a result of the plugin running when one packages using maven? It would be good to have a real config yaml file within the root folder of the application (or in a folder of the user's choice for that matter).
When one runs the plugin and installs the resulting debian package, I am aware that it replaces the mustache variables in the config yaml file and the resulting file is then stored in /etc/application-name.yml at the time of the package installation.
However this doesn't have an option to produce another config yaml file to run normally in commandline "java -jar target/application.jar server config.yml". So as expected when one tries to run their application on command-line, the mustache variables in the original config yaml file cause the following error :
Is there a way or options within the plugin to have multiple config yaml files produced (instead of the one which eventually ends in the /etc/application-name.yml) as a result of the plugin running when one packages using maven? It would be good to have a real config yaml file within the root folder of the application (or in a folder of the user's choice for that matter).