With the current launch options, current Capella-Studio 6.0.0 product does not ask for a repository path at launch.
The consequence is that when launching an other Capella-Studio instance, the workspace is in use. By default the associated behavior is to close the product and not allow to chose an other workspace => user is stuck an cannot launch another instance without modifying launch configuration.
Fix: add -Dosgi.dataAreaRequiresExplicitInit=true in the launch configuration of the product to fallback on the workspace choice when in use.
With the current launch options, current Capella-Studio 6.0.0 product does not ask for a repository path at launch.
The consequence is that when launching an other Capella-Studio instance, the workspace is in use. By default the associated behavior is to close the product and not allow to chose an other workspace => user is stuck an cannot launch another instance without modifying launch configuration.
Fix: add
-Dosgi.dataAreaRequiresExplicitInit=truein the launch configuration of the product to fallback on the workspace choice when in use.This is related to the 2021-06 migration (#133)