Bug 16921 - Problem importing plugins and fragments
Summary: Problem importing plugins and fragments
Status: RESOLVED DUPLICATE of bug 16114
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 critical (vote)
Target Milestone: ---   Edit
Assignee: Wassim Melhem CLA
QA Contact:
URL:
Whiteboard:
Keywords: readme
Depends on:
Blocks:
 
Reported: 2002-05-22 13:16 EDT by Lynne Kues CLA
Modified: 2002-09-26 12:28 EDT (History)
1 user (show)

See Also:


Attachments
.log (2.51 KB, text/plain)
2002-05-30 02:12 EDT, Dani Megert CLA
no flags Details
Problem dialog after importing plugins and fragments (21.38 KB, image/jpeg)
2002-08-21 04:17 EDT, Dani Megert CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lynne Kues CLA 2002-05-22 13:16:47 EDT
20020521 build.

1. Started with existing self-hosting workspace.  
2. Import ==> Plugins and fragments.
3. Click "Existing Binary Projects"
4. Finish. I got a problem message ==> "Could not delete 
org.eclipse.update.ui.win32".
5. Opened the import dialog again. Got a "Cannot find 
org.eclipse.update.ui.win32/.classpath" message.
6. Clicked "Existing Binary Projects".  
7. Explicitly clicked "org.eclipse.update.ui.win32" plugin.
8. Finish.  Worked this time.
Comment 1 Dani Megert CLA 2002-05-30 02:12:21 EDT
Plus one.
This happens every time but on "org.eclipse.ui.win32"

What's the state of my workspace: did the operation stop here or are the errors
collected and the one shown is the only one?

Increasing severity since if it leaves the user in a very uncomfortable
situtation:  am I ok if I only import "org.eclipse.ui.win32" again? Are the
others imported correctly? I think this is a must fix. If not for F2 then at
least for F3.

I attached the .log
Comment 2 Dani Megert CLA 2002-05-30 02:12:49 EDT
Created attachment 1117 [details]
.log
Comment 3 Lynne Kues CLA 2002-05-30 07:48:04 EDT
Yes, it seems to be getting worse.  With the latest build 0529, I had to 
physically delete directories in my workspace to get the import to work.  It 
seems like it is related to plugins with fragments.
Comment 4 Dejan Glozic CLA 2002-05-30 09:14:10 EDT
We didn't change this function for a while, so it must be related to changes in 
other components and/or new content in fragments that trips the 'sleeper' bugs.
Comment 5 Wassim Melhem CLA 2002-08-20 14:31:31 EDT
Lynne, Daniel,
Is the problem still occurring in 2.0?
Comment 6 Dani Megert CLA 2002-08-21 04:16:22 EDT
Yes still happens to me (see attached picture)
Note
1) I have autobuild off
2) I use an "old" pre-2.0 workspace i.e. not a fresh one setup for 2.0
Comment 7 Dani Megert CLA 2002-08-21 04:17:25 EDT
Created attachment 1867 [details]
Problem dialog after importing plugins and fragments
Comment 8 Lynne Kues CLA 2002-08-21 09:48:57 EDT
Ditto, still happens for me when using an existing workspace and importing 
plugins.  I get the same "could not delete" messages for the fragments that I 
am replacing.  If I run the import a second time and specify the fragments that 
weren't imported, the import works.
Comment 9 Wassim Melhem CLA 2002-09-26 12:28:25 EDT

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