Thanks for the clarification.
But it means that the bundle is incompatible with the "official" indexer..
Moreover don't use maven to generate our OBR; is that indexer useable oustide maven? maven is a development tool, while the OBR is "deployment time" on a production platform; it seems like two different worlds to me.

-arjun


On 09/20/2011 06:05 PM, Guillaume Nodet wrote:
I'm using the bindex code in the maven bundle plugin.
The code is actually in obr at [1] and the optional directive has been fixed
a while ago there.

Fwiw, I usually don't use bindex and I always create the obr constraints on
the fly programmatically using the interface at [2] and the createResource()
methods.

[1]
http://svn.apache.org/repos/asf/felix/trunk/bundlerepository/src/main/java/org/apache/felix/bundlerepository/impl/DataModelHelperImpl.java
[2]
http://svn.apache.org/viewvc/felix/trunk/bundlerepository/src/main/java/org/apache/felix/bundlerepository/DataModelHelper.java?view=markup



On Tue, Sep 20, 2011 at 17:24, Arjun Panday<[email protected]
wrote:
Guillaume,

which indexer are you using?
bindex-2.2 generates the requirements below and it breaks my OBR
resolution:

<require extend='false' filter='(service=org.osgi.**service.event.EventHandler)'
multiple='true' name='service' optional='false'>

      Import Service org.osgi.service.event.**EventHandler
</require>
<require extend='false' filter='(service=org.osgi.**service.log.LogService)'
multiple='true' name='service' optional='false'>
      Import Service org.osgi.service.log.**LogService
</require>
<require extend='false' 
filter='(service=org.osgi.**service.log.LogReaderService)'
multiple='true' name='service' optional='false'>
      Import Service org.osgi.service.log.**LogReaderService
</require>

/arjun




On 09/20/2011 05:14 PM, Richard S. Hall wrote:

On 9/20/11 11:10 AM, [email protected] wrote:

Author: gnodet
Date: Tue Sep 20 15:10:23 2011
New Revision: 1173181

URL: 
http://svn.apache.org/viewvc?**rev=1173181&view=rev<http://svn.apache.org/viewvc?rev=1173181&view=rev>
Log:
FELIX-3121: add back service manifest headers

Modified:
      felix/trunk/eventadmin/impl/**pom.xml

Modified: felix/trunk/eventadmin/impl/**pom.xml
URL: http://svn.apache.org/viewvc/**felix/trunk/eventadmin/impl/**
pom.xml?rev=1173181&r1=**1173180&r2=1173181&view=diff<http://svn.apache.org/viewvc/felix/trunk/eventadmin/impl/pom.xml?rev=1173181&r1=1173180&r2=1173181&view=diff>
==============================**==============================**
==================
--- felix/trunk/eventadmin/impl/**pom.xml (original)
+++ felix/trunk/eventadmin/impl/**pom.xml Tue Sep 20 15:10:23 2011
@@ -98,6 +98,14 @@
                           </Import-Package>
                           <Export-Package>org.osgi.**
service.event</Export-Package>
                           <Private-Package>org.apache.**
felix.eventadmin.impl.*</**Private-Package>
+<Import-Service>
+                            org.osgi.service.event.**
EventHandler;availability:=**optional;multiple:=true,
+                            org.osgi.service.log.**
LogService;availability:=**optional;multiple:=false,
+                            org.osgi.service.log.**
LogReaderService;availability:**=optional;multiple:=false

What is the 'availability' directive? Should that be 'resolution'?

->   richard

  +</Import-Service>
+<Export-Service>
+                            org.osgi.service.event.**EventAdmin
+</Export-Service>
                           <!-- Include concurrent lib but not sub
packages -->
                           <Embed-Dependency>
                               concurrent;inline="EDU/oswego/**
cs/dl/util/concurrent/[A-Z]*"





Reply via email to