"Maven-node-grunt-gulp-npm-node-plugin to end all maven-node-grunt-gulp-npm-plugins." A Maven plugin that downloads/installs Node and NPM locally, runs NPM install, Grunt, Gulp and/or Karma.
Apache License 2.0
4.2k
stars
868
forks
source link
Next to hard-coded environment variables support ".env" files as well #1155
Currently, we work with ".env" files managing our environment variables that should not be uploaded into Git. The plug-in cannot cope with it, and we have to run workaround scripts/commands around the actual Maven call. We want to run Maven without having to do this but for it to pick up the content of the ".env" files on its own.
If the current behavior is a bug, please provide the steps to reproduce.
%
What is the expected behavior?
Next to the environmentVariables configuration option, there is another one like environmentFile where the path to the ".env" file can be set. When the plug-in is running it is picked up and handled correctly.
Please mention your frontend-maven-plugin and operating system version.
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
Currently, we work with ".env" files managing our environment variables that should not be uploaded into Git. The plug-in cannot cope with it, and we have to run workaround scripts/commands around the actual Maven call. We want to run Maven without having to do this but for it to pick up the content of the ".env" files on its own.
If the current behavior is a bug, please provide the steps to reproduce.
%
What is the expected behavior?
Next to the environmentVariables configuration option, there is another one like environmentFile where the path to the ".env" file can be set. When the plug-in is running it is picked up and handled correctly.
Please mention your frontend-maven-plugin and operating system version.
Plug-in and OS independent.