The filter expression is wrong. By fixing the previous bug I actually introduced a null pointer exception and did not code the version correctly. This is now done correctly (I hope). I guess my bias against Require-Bundle shows a bit too much :-(

Kind regards,

        Peter Kriens




On 5 nov 2008, at 07:04, Stuart McCulloch wrote:

2008/11/5 Sriharsha <[EMAIL PROTECTED]>


version ranges specified with Export/ import packages are working fine. So bindex is doing its job in putting version ranges at repository.xml, but
i think OBR is unable to scan this information.
Is it a bug in bindex? or in OBR?
please suggest if I am going wrong anywhere.


you're assuming there's only one error - certainly I think that there may
well
be a bug in Felix's OBR implementation when resolving required bundles, but the last example repository.xml you posted was definitely incorrect:

   filter='(&amp;(symbolicname=Bundle2)(version&gt;=[1.0.0,2.0.0]))'

this is not a valid LDAP expression, so it looks like there's is still an
issue
to fix in bindex (expansion of required version ranges into LDAP format)
in addition to looking into the potential OBR issue.

PS. if you want the OBR issue investigated you should really open a JIRA issue at http://issues.apache.org/jira/browse/FELIX along with a testcase
and/or attached logs

see also a similar issue relating to fragments:

  http://issues.apache.org/jira/browse/FELIX-760

which also requires a version range fix to bindex

--
View this message in context:
http://www.nabble.com/bindex-tool-is-unable-to-retain-the-Require-Bundle-bundle-version-info-in-the-repository.xml-tp20297305p20336503.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Cheers, Stuart


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to