Community
Participate
Working Groups
Close a project. Replace with version. The project is re-opened. NOTES: JEM (6/5/01 10:13:58 AM) Replace with version menu item should be disabled on closed projects. JEM (6/6/01 12:48:50 PM) Fixed JEM (6/7/01 12:24:32 PM) Backed out, this is valid behaviour. There are cases where we don't want to be forced to open a project (and thus cause a build) just to be able to replace with another version. Ideally we could load in the new version in a closed state, but I don't think that's easy to do. Recommend no action. KM (6/8/01 3:03:59 PM) Closed is not just for builders, it indicates whether you are working on it or not (hence no children when closed). We should disable operation. I don't understand the usage case where I want it closed but want to replace contents given that when its closed I can't even see the original contents. JEM (6/8/2001 3:18:00 PM) John can perhaps explain better than I, but he often has a closed project and wants to replace it with another version without opening it first. Of course, in that case you would expect the newly-loaded version to be closed as well, which I believe is not possible currently.
{important/simple} PRODUCT VERSION: 118
As of build 20020321 the behavior is: 1. a closed project does not have a nature so Team operations don't appear. You can't replace with repository or anything else. 2. checking out a project from CVS to the name of the closed project, the user is prompted and the project is overwritten. This seems like good behavior to me.
fixed
GitHub Pull Request 141 created by [jonahkichwacoders] https://github.com/eclipse/che-docs/pull/141
