Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321214

Summary: Outgoing Change Sets don't contain the same files after Populate is run
Product: [Eclipse Project] Platform Reporter: Radek Wikturna <Roderick>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Attachments:
Description Flags
Eclipse configuration
none
Error log none

Description Radek Wikturna CLA 2010-07-29 07:07:55 EDT 
Build Identifier: Build id: 20100617-1415

I like using change sets. I use Synchronize view in the Outgoing mode, SVN Change Sets and Flat Presentation. After editing several java files, I see them in the list and I want to assign them to existing or new change sets. So I run Reasign Changes To (exising change set OR New Change Set...). So far so good. Lets say I have 5 change sets. When I close Eclipse and click on Populate in the Synchronize view, the change sets are gone, some are visible but they contain only some of the files that I assigned to them, so most of the files are in the folder <Unassigned>. So I have to do it again everytime I start Eclipse. With more and more files that are modified, the gets more frustrating!

Reproducible: Always

Steps to Reproduce:
1.Reasign edited files to existing/new change sets
2.close Eclipse
3.open Eclipse
4.run Populate in Synchronize view.
Comment 1 Radek Wikturna CLA 2010-07-29 07:08:33 EDT 
Created attachment 175482 [details]
Eclipse configuration
Comment 2 Radek Wikturna CLA 2010-07-29 07:08:51 EDT 
Created attachment 175483 [details]
Error log
Comment 3 Radek Wikturna CLA 2010-11-23 04:16:05 EST 
The problem is still reproducable in the latest Eclipse 20100917-0705 (Helios Service Release 1). Could anyone at least assign this problem to someone?!
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:03:41 EDT 
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 5 Eclipse Genie CLA 2021-08-29 00:50:30 EDT 
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.