On 23 February 2011 10:19, Guillaume Nodet <[email protected]> wrote: > On Wed, Feb 23, 2011 at 11:00, Alasdair Nottingham <[email protected]> wrote: >> Hi, >> >> I want to +1 on Zoe's concern here. I also have a few more observations: >> >> In OSGi 4.3 you can install the same bundle multiple times, i.e. I can have a >> bundle with symbolic name a.b.c and version 1 and I can install it 20 >> times assuming >> the location is different. In this situation having multiple jars >> containing a.b.c at version 1 >> would not produce an error, and would be a problem in my view. > > I think the argument does not hold as i'll be able to install using > > http://repo1.maven.org/maven2/org/apache/aries/blueprint/org.apache.aries.blueprint.core/0.3/org.apache.aries.blueprint.core-0.3.jar > > http://repo2.maven.org/maven2/org/apache/aries/blueprint/org.apache.aries.blueprint.core/0.3/org.apache.aries.blueprint.core-0.3.jar > file:deploy/org.apache.aries.blueprint.core-0.3.jar > and the same problem would happen. I suppose if you put the framework > in this mode you need a deployment agent smart enough to handle the > deployments. > >> I personally think most people who use aries will want the pre-built >> binaries, rather than the >> source zips, so I think we should be focusing on making that easy to >> do and I don't think that >> requires us to release in this way. > > That's actually my main concern too. Forcing the user to find a > correct combination of bundles that work together because each of > those have a different version, does not seem to go in the right > direction for me.
To solve the problem of indicating to the user what works together we could create an Aries distribution a zip of all the bundles that we've tested work together. We'd have bundle releases and distribution releases. Each bundle could be released fairly independently of each other. (Clearly if an API bundle has a minor version change then the impl bundle will need to be released at the same time). The distribution can be released independently of bundles. Using a a distribution release (we can finesse the name), users get the most confidence that bundles work together. Using individual bundle releases on top, things should still work but there's no statement that we've tested the combination of bundles / bundle versions that they have. Jeremy
