Re: [orbit-dev] Remove of ".orbit" suffix from recipes

["David M Williams" <david_williams@xxxxxxxxxx>]

> > A client hit a situation where we had a conflicting bundle between
> two bundles.  Turned out the older bundle came from Orbit, but
the 
> project started including putting in OSGi metadata.  It was hard
to trace.
> 
> At this time, Bundle-Vendor (thanks Andreas) is your only option.
> Having that that, please file a feature request with Eclipse 
> Buzilla. The decision to drop ".orbit" was done for the
transition 
> vom CVS to Git only. It should be possible to revisit after the transition.
> 

It can be revisited, but I can't imagine that changing
the bundle id would 
ever be the right answer. Besides the Bundle-Vendor:header, and the Eclipse signature 
already mentioned, the other "OSGi way"
to distinguish bundles with same id and package names, 
is to use arbitrary attributes on Orbit's "exported"
packages. (such as "source=Orbit;"). 
I know this is normally used for "matching"
on other people's "import packages" (if they care). 
What I do not know is if OSGi runtime allows a "negative
match" to be specified (i.e consumer does
not want "source=Orbit"). 

Just thought I would mention this (again) now, so
interested parties can research deeper. 

= = = = = 

I would also be interested in hearing how the client
ended up with conflicting bundles. 
Was it just from "installing different things"?
Or was it because their own build was 
not precise enough? Or ... something else?

= = = = = =

Thanks,