change-to command checks out across branches
If kepler is currently in a branch, the change-to command should not update from the trunk. Once a branch is selected with the -Dbranch=xxx param, the build system should keep the current workspace in the branch until the user updated to another branch or the trunk. The build system should also print a banner alerting the user that he/she is working in a branch to avoid confusion.
this bug arose when we added several modules to the trunk. Matt was working in a branch (unknowingly) and when he ran 'ant change-to -Dsuite=kepler' it updated the kepler/module-info/modules.txt file from the trunk, but did not update the rest of the modules to the trunk so the build failed. The build-area was also running from the branch so the excludes file was not updated and would not allow him to build ptolemy.
#1 Updated by David Welker over 9 years ago
What is the purpose of the -Dbranch option? All branches should be named differently, so this option should not be necessary. If the branch has a standard name and is stored in the standard location, the build knows where to look. If the branch does not have a standard name or is not in the standard location, simply add the module name and location to registry.txt and the build will know where to look. The only limitation is that you cannot have a branch with the exact same name. But, that limitation is a feature, not a bug.
In my view, this bug should be eliminated by removing the -Dbranch option from the change-to command.