Hi @all,
situation is as follows: a subproject (DEF) in a toplevelproject (ABC) has its initial checkpoint 1.1. In this checkpoint it contains nothing, not any subproject and not any member. Later it was becoming a new subproject (named GHI), which is included in checkpoint 1.2, and even later this subproject gets some members. Now the users wanted to branch from checkpont 1.1 and they became a devpath 1.1.1.1, which contains (as expected) also nothing.
But now the users wanted to create a subproject with the same name "GHI" as the one in the mainline, but not a share from the mainline and also not an "add". They made a variant sandbox, and within these sandbox they tried "create subproject". It downst work. Integrity throws some weired exceptions:
mks.frame.app.commands.PreconditionFailedException: mks.frame.app.commands.PreconditionFailedException: The project #/ABC/DEF#b=1.1.1.1#GHI could not be located on the server <serverhostname>:7001: MKS125212: The project file /ABC/DEF/project.pj is not registered as a top level project with the current server.
[...]
Huh?
At the end it seems not to be possible to get a subproject in the devpath with the same name as in the mainline, but independent from the one in the mainline? are there any options to set at the server or the client to prevent Integrity from doing such courious things?
kind regards, Jens