Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 230027 - Create patch default projects not always correct
Summary: Create patch default projects not always correct
Status: RESOLVED DUPLICATE of bug 201714
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-02 16:10 EDT by DJ Houghton CLA
Modified: 2008-05-02 17:39 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description DJ Houghton CLA 2008-05-02 16:10:12 EDT 
3.4 M7

I (and others) have run across situations where we select a group of projects in the Synchronize view and choose Create Patch... and then just hit Finish without really looking at the dialog. Then we later find out the resulting patch doesn't contain everything we thought it would. 

It turns out that sometimes the dialog doesn't have all the projects selected that we had selected in the view when choosing the menu item. I don't have a reproducible case for this but it seems to happen frequently.
Comment 1 John Arthorne CLA 2008-05-02 16:50:56 EDT 
This just happened to Simon as well in bug 218642.
Comment 2 Szymon Brandys CLA 2008-05-02 17:20:02 EDT 
(In reply to comment #0)
> It turns out that sometimes the dialog doesn't have all the projects selected
> that we had selected in the view when choosing the menu item. I don't have a
> reproducible case for this but it seems to happen frequently.
>
 
So the list in the dialog doesn't contain all selected projects or the list is complete but not all projects are checked?

This looks like a duplicate of bug 201714.
Comment 3 John Arthorne CLA 2008-05-02 17:39:44 EDT 
Yes, looks like a duplicate.

*** This bug has been marked as a duplicate of bug 201714 ***