Alan D. Cabrera wrote:
On Dec 26, 2008, at 11:49 AM, Richard S. Hall wrote:
Old revision:
exports foo v1, bar v1, cdr v1
New revision:
exports cdr v2, car v1
imports foo v1 (from old revision), bar v1 (from old revision)
So, it seems that we have bundles within bundles.
Each bundle may have multiple revisions after update(s), but before refresh.
This is assuming there are no uses constraints that prevent it.
So, we add a new archive bundle and have to have both resolved. The
old one "automatically" resolves since was previously resolved. The
new one then must be resolved or else it's exports are not available.
The old revision is never unresolved, because it has people using it,
but in effect you are correct.
Also, we have had some debate inside CPEG as to whether old packages
are available for new wires. My position is that they are.
I'd love to see the debate thread since to my mind there can be no
other position than yours.
Amen.
-> richard
Regards,
Alan
-> richard
It seems that much of this is logically "intuited" from the spec.
Regards,
Alan
Alan D. Cabrera wrote:
Let's say I have a bundle that exports packages com.a.foo:1.0.0,
com.a.bar:1.0.0, and com.a.cdr:1.0.0. There are a number of
bundles that import com.a.foo.
Now, we update the bundle and the new bundle archive exports
com.a.foo:1.0.0, com.a.bar:1.0.0, com.a.cdr:2.0.0, and
com.a.car:1.0.0. I'm not sure what happens. I think that since
the old bundle archive has an export, com.a.foo:1.0.0, that's
being used nothing happens until a framework restart or the
package com.a.foo is refreshed.
Am I correct?
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
