Bug 232052 - Java files excluded from build path appears 2 times in CVS syncrhonize view
Summary: Java files excluded from build path appears 2 times in CVS syncrhonize view
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-14 08:01 EDT by utilisateur_768 CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description utilisateur_768 CLA 2008-05-14 08:01:30 EDT
Build ID: I20080502-0100

Steps To Reproduce:
I don't know how to reproduce it

More information:
I've excluded 2 files from the build path of a java project, and the files appears 2 times in the synchronize view.

They appaears as new files, since i've changed their names.
Comment 1 utilisateur_768 CLA 2008-05-14 10:06:10 EDT
In short i have 4 [outgoing addition], 2 with the filles blue J icon, and 2 (with the same names) with the empty blue J.

The bug does not reproduce in the "Workspace" model. So should it be reassigned to JDT UI ?
Comment 2 Tomasz Zarna CLA 2008-05-14 10:52:15 EDT
Did you sync before or after excluding the classes from the build path?
Does sync'ing again make the two CU (the ones with blue J) go away?
Comment 3 utilisateur_768 CLA 2008-05-14 12:05:01 EDT
Synchronizing again (not updating) does not make any files go away.
Comment 4 utilisateur_768 CLA 2008-06-17 09:01:54 EDT
Build ID: I20080609-1311

Today i got it again, when i tried to remove a java file (excluded) i realized that a second normal java file was present with the same filename (in the same package). Only the icon is different : filled blue 'J' vs "empty" blue 'J'.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:15:12 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.