Community
Participate
Working Groups
# Activate a task # Change a file # Close that file's project # Activate a different task # Open the project # The changed file has moved to the active change set
Sam, do you know if this happens without a task being active as well? You can select a default change set through the context menu in the synchronize view.
Yes, it happens also when setting a change set to default with no task active.
Thanks for checking. Sounds like Mylyn's change set management inherits the behavior of the platform. I'll move this to team to see if this has been discussed before. Sam, can you describe the behavior you expect?
When a project is opened, I would expect changed files within it to appear in the same change set(s) they were in when the project was closed.
Is this a regression? Is there a previous version of Eclipse that works like you would expect or was it always like that? I don't recall making any changes in this area.
I don't know if it ever worked as I would expect.
I has probably been that way all along and is not a regression. I moved it here to get input why it was implemented the way it is and thoughts on changing the behavior as Sam suggested.
I agree, this is not what I would expect either. Apparently, when reopening the project, the check made in ChangeSetContentProvider.isContainedInSet(IDiff) returns false even for IDiffs which were part of the change set before closing the project. Maybe they're removed from the set when closing the project? Haven't checked that though, just a guess.
Created attachment 201808 [details] mylyn/context/zip
Still here in 4.4. this is very annoying, you work on a few change sets then close the project and all of them are gone.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
