Redesign the relationship between Liberty module and run configurations.
[ ] Custom params and the 'run in container' option must be set in one call.
[ ] Alternatively the Liberty module should hold a reference to the last used run config. Then we need to remove this reference if the run config is deleted. Or mark the run config as invalid when deleted.
The current work flow supported is:
Use Start... Liberty action and type some parameters and check the Run in container checkbox. Click Run.
Stop the server.
Use the Start Liberty action. You expect the server to start with the same parameters as the first step.
This behaviour is similar to Eclipse. We can discuss with the guild if this is what we really want because VS Code may not do this. Also we should examine how other IntelliJ run configs work and decide whether Liberty tools should be consistent platform to platform or if the launch behaviour on each platform should be the same for all languages or servers on that platform.
TrevCraw
commented
2 days ago
Redesign the relationship between Liberty module and run configurations.
The current work flow supported is:
Start...Liberty action and type some parameters and check the Run in container checkbox. Click Run.StartLiberty action. You expect the server to start with the same parameters as the first step.This behaviour is similar to Eclipse. We can discuss with the guild if this is what we really want because VS Code may not do this. Also we should examine how other IntelliJ run configs work and decide whether Liberty tools should be consistent platform to platform or if the launch behaviour on each platform should be the same for all languages or servers on that platform.