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

Bug 328144

Summary:	self-updating eclipse with a changed launcher plug-in causes troubles
Product:	[Eclipse Project] Equinox	Reporter:	Helmut J. Haigermoser <helmut.haigermoser>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	critical
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Helmut J. Haigermoser

2010-10-19 11:20:13 EDT

Build Identifier: 3.6 final

My RCP product just tried to update itself from 3.6 base to 3.6.1. Along the way I had built a new "org.eclipse.equinox.launcher" bundle.

After the RCP went down for the restart it never came back up, with this message being printed on command line:

"Unable to access jarfile /tmp/helmuth/test_update/maintenance/wrInstaller/x86-linux2/plugins/org.eclipse.equinox.launcher_1.1.0.<old>.jar" (<old> was the old build-id).

This was only a problem on unix, the garbage collector did not have a chance to throw away the windows launcher plug-in while it was in use I guess (not sure about that though..)

Looks like the garbage collector is cleaning up after the update, which is fine I guess. The new <product>.ini even contains the new line 
<pre>
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.<new>.jar
</pre>
, but somehow the EXIT_RESTART of my application does not seem to re-read the ini file or has some cache.



Reproducible: Always

Steps to Reproduce:
1. Have an RCP base on 3.6, install it
1.1 The RCP has a -vm <vm location> argument, not sure if that matters though
2. Update that RCP to a newer base, 3.6.1, have 3.6.1 include a new launcher bundle
3. Watch the failure on linux

Comment 1 Helmut J. Haigermoser

2010-10-21 08:09:46 EDT

Guys, I'm marking this as a duplicate of the real problem:
The SimpleProfileRegistry changed in 3.6 such that it does not recognize the SELF profile for our RCP anymore. Debugging the issue and recognizing the faulty part lead to a workaround we can release with but I'm still hoping we can work together in getting the profile registry fixed.. :)
Helmut

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