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

Bug 137207

Summary:	3.2RC1 can't import update sites created with 3.2RC1
Product:	[Eclipse Project] Platform	Reporter:	Kirby Bohling <computerslicer23>
Component:	Update (deprecated - use Eclipse>Equinox>p2)	Assignee:	Platform-Update-Inbox <platform-update-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	computerslicer23, Michael.Valenta, sja.eclipse
Version:	3.2
Target Milestone:	3.2 RC2
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:	137614
Bug Blocks:

Description Kirby Bohling

2006-04-18 09:31:39 EDT

Create a new feature project (org.example.feature).  Add org.apache.ant as a plug-in.  (Chosen specifically because it usable by Eclipse 3.1).  Use the wizard to create an update site (org.example.update.site).  It doesn't work if you don't use the wizard, but the wizard is the quickest way to reproduce the bug.  Click build all wait for that to finish.  Copy the contents of the update site project to a local folder.  Now use the update manager with a local site to import.  Under 3.2RC1, it hangs indifinitely at 33% during the "Initializing" of the update manager.  Start up a 3.1.2 version of Eclipse use the Update Manager and add the local site.  That feature set imports just fine.

I have successfully imported update sites exported from 3.1 into 3.2RC1.  So I am not sure exactly where the bug is, but it's consistent.  I have successfully added all of the updates from the Callisto Discovery Site that is in 3.2RC1's update manager just fine.  Which shows that 3.2RC1 can import Updates.  Update sites generated using 3.2RC1 can import into 3.1.  But import sites create w/ 3.2RC1 can't be imported into 3.2RC1.

Comment 1 Kirby Bohling

2006-04-18 10:24:05 EDT

Adding myself to the CC list.

Comment 2 Branko Tripkovic

2006-04-18 22:19:57 EDT

Does this happen with any plugin or just with org.apache.ant?  I saw similar behavior  and i had to put progress monitor in the background to get to install window. Is this what you are experiencing?

Comment 3 Kirby Bohling

2006-04-19 11:46:50 EDT

Yes, you seem to have the same experience.  I have to "Run in the Background" to get back to the app.  I can cancel out of that (at points, this will leave you in a corrupt state if you cancel and close Eclipse, but I'll call that user error, killing an operation during meta-data update is a bad idea).

I had the same problem with a number of plug-ins.  I tried to re-package a number of binary plug-ins to simplify internal development.  I can't say for certain that I packaged a feature from source code, but I believe I did.  We distribute archive sites internally that include all of the common third party libraries for 3.1.  We have some interest in using 3.2 so I was assembling the archive that included a number of third party plug-ins we use for the 3.2RC1 for internal testing.

Comment 4 Branko Tripkovic

2006-04-19 14:14:18 EDT

If everything was functioning probably you would not be able to press cancel at that time. It's bug outside of update. We are investigating. These two things (download and install) are meant to happen one after another not along side and that is what is causing this problem. Workaround is to put download progress window in the background and it will disappear once you finish installation of plug-in.

Comment 5 Tod Creasey

2006-04-24 16:41:02 EDT

I have just tried this with N20060424-0100 and the problem no longer occurs so I think Bug 137614 is resolved with my rollback.

If you could verify during the test pass that would be much appreciated.

Comment 6 Dejan Glozic

2006-04-24 17:14:18 EDT

*** Bug 138266 has been marked as a duplicate of this bug. ***

Comment 7 Dejan Glozic

2006-04-24 22:21:59 EDT

*** Bug 128449 has been marked as a duplicate of this bug. ***

Comment 8 Branko Tripkovic

2006-06-26 15:46:01 EDT

Fixed in rc2 Tod. Thanks Tod.