Hi, This is a bug. David raised it last week. I thought I committed a fix. I don't have svn access right now, but there was a JIRA, so look there.
Alasdair Nottingham On 27 May 2011, at 05:19, Jarek Gawor <[email protected]> wrote: > Hi, > > I think I've ran into a problem with deploying a resolved application. > Application that has DEPLOYMENT.MF with exact bundle versions (e.g. > deployed-version=1.0.0). > > The OBRAriesResolver.getBundleInfo(String, Version) is called during > application installation to get the location of a bundle with the > exact version as specified in DEPLOYMENT.MF. However, looking at the > code, the filter that's generated to query the OBR only specifies a > minimum version (i.e. &(version >= 1.0.0)) instead of a range (i.e. > &(version >= 1.0.0)(version <= 1.0.0)). So that means that it is > possible for getBundleInfo() to return information for a bundle with a > higher version then requested. And that totally breaks the purpose of > the DEPLOYMENT.MF. > > Did I miss something or is this a nice bug? > > Jarek
