Marcin Grabda
Marcin Grabda
I have just stumbled upon the same issue... It would be good to handle it more gracefully...
Is there any workaround?
1. grunt-run 0.3.0 2. node 0.10.35 (tried also with 0.12.3) 3. My configuration: ``` var grunt = require('grunt'); module.exports = { backend: { cmd: 'java', args: [ '-jar', grunt.file.expand('../build/libs/*.jar') ],...
I'm starting this process as a first task in a series of tasks in grunt: ``` grunt.task.run(['run:backend', '...']); ``` I was investigating the issue, when I realized that once the...
Even if I move it there, don't we still need the variable?
How can I test that? I mean, is this in any way supported?
Ok, I will look into that and try to fix it. I didn't consider it when making the changes and it definitely breaks this functionality.
I have been using the application with my changes for 3 weeks already and it seems to work fine with one window. I am not really sure how it should...