Well, if it makes a difference for you, you should specify the import
version. If no, who cares?
Kind regards,
Peter Kriens
On 20 sep 2008, at 18:01, Richard S. Hall wrote:
Your belief is correct, but it also comes down to whether the
package is already "in use" or not. If it is already in use, then it
will use the existing version rather than creating a new class
space. If you know for sure that it is not in use, then perhaps
Felix is incorrectly determining that it is in use. If so, perhaps
you could create a JIRA issue with.
Of course, it is also possible that the versions are not getting
sorted properly when choosing candidates, but I don't think that's
the case.
-> richard
Pierre De Rop wrote:
Hi all;
1) I have a bundle *B* which imports the following package:
* Import-Package: javax.xml.bind
2) The System bundle re-exports the* jdk1.6 *javax.xml.bind with
version 1.6.0, (see felix.properties):
jre-1.6=, \
....
javax.xml.bind; \
version="1.6.0"
3) I also have packaged jaxb in a bundle *JAXB.jar* and this bundle
exports the javax.xml.bind with version="2.1.4"
Export-Package: javax.xml.bind;version="2.1.4"
I have observed that if I don't force the version "2.1.4" in the
Import-Package of the bundle B, then B is wired with
version "1.6.0", not with the highest version "2.1.4";
So is a normal behaviour ?
I thought that the framework was supposed to wire the bundle B with
the highest version of the package "javax.xml.bind" (2.1.4).
(As far as I remember, though, I think that Knopflerfish wires B to
the highest version).
Best Regards
/pierre
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
