Hi all,
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
Are you updating the loginscreen bundle when you see the bundle get started
twice or do you have multiple versions of the loginscreen bundle? If a new
version of the loginscreen bundle is being provisioned then this is
expected behavior. I would have expected the loginsreen bundle to bring
down