Bug 98688 - bin/.project created while importing existing project in my workspace
Summary: bin/.project created while importing existing project in my workspace
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 RC2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-07 10:53 EDT by Frederic Fusier CLA
Modified: 2005-06-08 08:09 EDT (History)
0 users

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 Frederic Fusier CLA 2005-06-07 10:53:16 EDT 
Using build N20050607-0010 + JDT/Core HEAD

I've 2 eclipse sessions opened on 2 different workspaces (of course...).
1) Create project Test in workspace 1
2) Create a class X in this project
3) In workspace 2, Import existing project "Test" from workspace 1
4) Expand project "Test" in package explorer: I can see a bin folder with a
.project...!?

Note that this happens both with RC1 and RC2, but I do not remember have this
strange behavior before... (I often import existing project in my test workspaces)
Comment 1 Frederic Fusier CLA 2005-06-07 11:15:46 EDT 
I confirm that this does not happen with 3.1 M7.
However, it seems that this cannot be reproducible systematically... :-(
I'll try to understand when exactly it can be reproduced and reopen it when I
get it...
Comment 2 Frederic Fusier CLA 2005-06-07 11:30:19 EDT 
It seems that Test class need to have compiler error...
I get this unexpected bin/.project with following class Test.java:
import java.util.HashMap;
import java.util.List;

public class Test<T> {
	List<String> x;
	HashMap<String, String> y;
	foo() {}
}
Comment 3 Frederic Fusier CLA 2005-06-07 11:33:36 EDT 
Now that I have find a scenario to reproduce it, I can really confirm that it
does not happen with 3.1 M7...
Comment 4 Dirk Baeumer CLA 2005-06-07 13:42:19 EDT 
Import existing prject is a workspace operations. 

Frederic, I don't think that this is a UI problem. The bin folder is under
JDT/Core control. We never put anything there. Could it be that the builder
wrongly copies the file.
Comment 5 Dirk Baeumer CLA 2005-06-07 13:43:07 EDT 
Wanted to say that Import existing projects is a Platform/UI operation.
Comment 6 Jerome Lanneluc CLA 2005-06-07 15:58:08 EDT 
Looks like a dup of bug 96258
Comment 7 Olivier Thomann CLA 2005-06-07 20:49:17 EDT 
If this is a dup of bug 96258, then Frédéric should not be able to reproduce it
with the build he used.
Bug 96258 has been verified with the same build used to reproduce this one.
Comment 8 Jerome Lanneluc CLA 2005-06-08 07:08:10 EDT 
Cannot reproduce with N20050608 + JDT/Core HEAD
Comment 9 Frederic Fusier CLA 2005-06-08 08:09:32 EDT 
In fact this problem seems to occur only while importing project from RC2
workspace to RC1 workspace
I agree I never was able to reproduce it while importing project from RC2 wksp
to RC2 wksp...
I've also verified that importing project from RC1 wksp to RC2 wksp works
properly and does not create this unexpected bin/.project file.

Close as invalid as failing test case does not reflect a real life scenario, it
was just specific for testing...