You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently any continuous process such as gulp watch, webpack watch will stop the maven execution.
What is the expected behavior?
The exec-maven-plugin mentioned in README supports following options:
async- If set to true the child process executes asynchronously and build execution continues in parallel.
asyncDestroyOnShutdown - If set to true, the asynchronous child process is destroyed upon JVM shutdown. If set to false, asynchronous child process continues execution after JVM shutdown. Applies only to asynchronous processes; ignored for synchronous processes.
It would be great if this plugin allows the same so that we don't need to start such tasks manually from another terminal.
The text was updated successfully, but these errors were encountered:
I'd also love to have this feature. In my case I have multiple child projects that need to build frontend code and I'd like to be able to automatically set a watch build on all of the child projects from maven so devs don't need to make sure they are using the same node version when they want to do a watch build. Instead they could just run a maven command that kicks off all the relevant watch builds and kill maven when they were done.
Thanks for making such a great plugin!
Do you want to request a feature or report a bug?
feature
What is the current behavior?
Currently any continuous process such as
gulp watch
,webpack watch
will stop the maven execution.What is the expected behavior?
The
exec-maven-plugin
mentioned in README supports following options:It would be great if this plugin allows the same so that we don't need to start such tasks manually from another terminal.
The text was updated successfully, but these errors were encountered: