So if simple configurator comes to picture there’s no way to guess whether the “initially installed” framework and the one listed in bundles.info are the “same”?
I saw equinox location is “system bundle” so if it’s presented in bundles.info there’s no way to prevent second installation of the framework … which is a kind of strange and is causing issues in Virgo scenario.
(“Initially installed” – the one that hosts simple configurator before its first start )
There is a bug describing the issue in more details:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=350356
Comments are welcome.
Thanks,
Katya
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Watson
Sent: Monday, June 27, 2011 4:17 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Multiple bsnversion in equinox
Yes this is correct. Where the bits are located on disk has no influence on if the installation of the bundle is considered unique or not. The location string is treated as opaque by the framework when determining if the installation location is unique or not.
Tom
"Todorova, Katya" ---06/24/2011 11:13:33 AM---So location uniqueness is based on simple string comparison?
From:
| 
"Todorova, Katya" <katya.todorova@xxxxxxx>
|
To:
|
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
|
Date:
|
06/24/2011 11:13 AM
|
Subject:
|
Re: [equinox-dev] Multiple bsnversion in equinox
|
So location uniqueness is based on simple string comparison?
I thought Equinox resolves the string passed as location and compares files to which locations point...
So you say that if I install ./temp/my.jar and ./temp/../temp/my.jar it will result in two bundles installed and that's the correct behaviour?
Thanks for your help,
Katya
-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of John W Ross
Sent: Friday, June 24, 2011 6:25 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Multiple bsnversion in equinox
I'm not sure I understand why you're surprised?
If you install a bundle with the same location and the already installed
bundle is visible to the context, the install will succeed and you will
receive a reference to the already installed bundle. If the already
installed bundle is not visible to the context, the install will fail and
you will receive a BundleException indicating the operation was rejected
by a hook. This will happen regardless of the value of the bsnversion
property because locations must be unique.
If you install a bundle with the same bsn and version as an existing
bundle, and the location is unique, and the bsnversion property is set to
'single', the install will fail and you will receive a BundleException
indicating the bundle is a duplicate. If the bsnversion property is set to
'multiple', the install will succeed and you will receive a new Bundle
object with a unique ID. Whether or not the bit source is the same should
not make any difference as far as I know.
~ John
"Todorova, Katya" <katya.todorova@xxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
06/24/2011 08:27 AM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
[equinox-dev] Multiple bsnversion in equinox
Hi,
I start Equinox with org.osgi.framework.bsnversion=multiple and try to
install one bundle twice:
osgi> install reference:
file:C:\eclipses\eclipse-SDK-3.7RC4-win32-x86_64\eclipse\plugins\com.ibm.icu.source_4.4.2.v20110208.jar
Bundle id is 5
osgi> install initial@reference:
file:C:\eclipses\eclipse-SDK-3.7RC4-win32-x86_64\eclipse\plugins\com.ibm.icu.source_4.4.2.v20110208.jar
Bundle id is 6
The installation is successful even if locations strings are not equal but
resolve to the same file.
Is that expected?
Thanks,
Katya_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
