Bash configuration are not launched when multirun configuration is debugged

[ssssteffff]

Hi, I would like two launch several configurations at once (bash and Maven configurations) :

• run bash ones
• debug maven one

If I run the multirun configuration, both are run.
If I debug it, only maven configuration is actually debugged, and bash configurations are simply ignored. (Probably because bash configurations cannot be debugged).

Could it be possible to, either let the user choose between run and debug for every configuration (within multirun configuration) or, to debug configurations when possible, run them otherwise?

PS: this issue is related to #36, I didn't know if it was preferable to comment it are open a new one.

[dustinjohnson13]

Related, I'm attempting to use Debug With JRebel for an application server and also run an NPM script (webpack dev server). When using Debug With JRebel option, the NPM configuration fails to launch.

As a workaround, I created a Groovy class that simply runs the appropriate NPM command in the console and used that as my launch configuration. A bit hacky, but it works.

[GaldanM]

Hello, are you planning on implementing this feature ?

I'm trying to run a bash command to launch Node.js in a docker container then listen to it in debug mode.

I run bash command with BashSupport plugin but this one can't be launched in debug mode.

[rkhmelyuk]

Hi,

Unless someone from requesters is ready to invest time and resources to add this support, I believe there is little chance this will be implemented.

navels@ and community do a great job to keep the plugin updated to support newer IJ versions. But adding new functionality or fixing bugs, that aren't mainstream, is probably too much of investment to ask them.

Can you get the necessary functionality with built-in compound configuration https://www.jetbrains.com/help/idea/run-debug-configuration-compound-run-configuration.html ?