Expected behavior ----------------- Check out a project to /path/to/projectA. Configure CROPS to use that workspace. Work with project as expected. Check out a project to /different/path/to/projectB. Configure CROPS to use that workspace. Work with project as expected. Observed behavior ----------------- CROPS workspace is preset to $HOMEPATH/crops-workspace. Project must be in that folder before they can be built.
This doesn't apply to crops-py. The crops installer is obsolete and won't be maintained going forward.
reopening
The current plan for the eclipse-crops plugin is to spin up a new CROPS toolchain container for each workspace, perhaps even for each build. The host/container mapping would then be setup for each specific instance of running container. Or do we also want a CLI/RESTful API path for this?
This is fixed by using the samba containers and docker volumes. Bug 10452 is still needing to be done to fully flesh out the options but currently you can solve this by using subdirectories of the volume for different attached containers. within those subirectories, multiple workspaces function.