Hi all, Since a few releases GoGo uses a cap/req model to get a complete set of bundles (shell, runtime, command). While this makes sense in most cases, this introduces a new problem for us. When creating a component that implements some commands, it is now always coupled to the shell bundle as well. This adds (IMO) unneeded dependencies, which could have been optional. Eg when testing that component I now have to include the shell, which in turn requires the commands as well. This also requires me to update runconfigurations to use the nointeractive flag for a headless environment.
Perhaps I'm overlooking something, but is there a clean way to solve this with the current gogo version? In previous versions I could just add the runtime and everything would resolve as expected. Thanks! -- Met vriendelijke groet, Alexander Broekhuis
