[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] bundle starting twice
- From: "Tom Huybrechts" <tom.huybrechts@xxxxxxxxx>
- Date: Mon, 5 Jan 2009 21:37:30 +0100
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=Sfada1ldtWjfG30us2uLSYjE/3sx/oK77eEGIICvxHbCIg7bFh35hXsrKJOzIjLPos uOOHiUVBD22ScEpYZyykm+tHM7urb5M8+FuIdtTgXEK8MaODanPZZuiyqb/gN8HWf+DI hVfZEdVZuNPM/mBbhy09wTkooBeL0Jn7ZNb+w=
I have a client application in which I added a bundle ('loginscreen')
at start level 1 to display a login screen.
While this screen is presented to the user, the framework startup
continues as usually, with org.eclipse.update.configurator at level 3.
Now when modifications have occurred to the set of available bundles,
Package Admin will always stop my loginscreen bundle, and restart it.
In this case that means there will be two login screens...
The loginscreen bundle only depends on the framework, and no other
bundles depend on it, so I don't see why it would need to be
Can I avoid this behaviour somehow ? I don't want to start the bundle