On Dec 26, 2008, at 3:28 PM, Richard S. Hall wrote:
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.
When a bundle updates, I guess it can switch from being a fragment
bundle to a host bundle depending on the contents of the updated
bundle. Can the symbolic name change so long we there is no other
bundle with that name and version? I don't see where it says that it
cannot.
Regards,
Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
