You may want to not align compile time dependencies (the maven deps) with the runtime dependencies (bundles listed in features). You can safely depend on the overall compendium jar at build time, this can ease the build a bit. At runtime, you should depend on a feature which will provide the DS implementation and packages.
2016-03-01 13:52 GMT+01:00 Mike Rumpf <mike...@gmx.de>: > Of course I read that before. However for development you will need the ds > annotation classes which are not part of the scr bundle. You will nee the > part of the compendium bundle to make it work. > > I just configured a JPA/JDBC for hibernate/postgres solution in karaf. The > same applies here: I needed the jdbc/jpa parts from the compendium as well. > In the past we provided manually created osgi jdbc/jpa bundles with the > interfaces. Nice to have them now at maven central. > > But maybe I am missing something. Is there a way to avoid using them? > > Mike > > > maggu2810 wrote > > Have you read this one: > > > http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-osgi-faq.html#should-a-service-providerconsumer-bundle-be-packaged-with-its-service-api-packages > > Christian Schneider posted the link already above > > > > If you have a look at > > > http://search.maven.org/remotecontent?filepath=org/apache/felix/org.apache.felix.scr/1.8.2/org.apache.felix.scr-1.8.2.jar > > you will see, that this bundle contains the OSGi service interfaces. > > If you have a look at > > > http://build.eclipse.org/rt/virgo/ivy/bundles/release/org.eclipse.virgo.mirrored/org.eclipse.equinox.ds/1.4.200.v20131126-2331/org.eclipse.equinox.ds-1.4.200.v20131126-2331.jar > > you will see, that this bundle does not contain the OSGi service > > interfaces. > > > > 2016-03-01 13:17 GMT+01:00 Mike Rumpf < > > > mikey99@ > > > >: > >> maggu2810 wrote > >>> It has been some time ago, I had to use the Equinox Event Admin and DS > >>> implementation. > >>> That bundles (I have not checked other versions) missing the APIs - > >>> they contain only the implementation. So I have to create a splitted > >>> compendium myself to get them working in Karaf. > >>> I read this blog and I am fine, that such packages exist. > >>> > >>> I do not see a use case for interfaces without implementations. > >>> > >>> But hey, it is up to you how you use this artifacts. > >> > >> Isn't that still valid? The OSGi JPA/JDBC interfaces are only available > >> in > >> the respective osgi interface bundles as linked in the blog. As far as I > >> know there is no apache felix bundle to provide the service interface > >> classes. Same goes with the OSGi ds annotation classes. Therefore the > >> bundles listed in the blog are very helpful. However the JPA bundle has > a > >> dependency to javax.persistence [1.1,2) which cannot be resolved > >> easily... > >> Seems to be a bug. > >> > >> Mike > >> > >> > >> > >> -- > >> View this message in context: > >> > http://karaf.922171.n3.nabble.com/OSGi-Compendium-within-a-feature-restarts-the-console-tp4045606p4045643.html > >> Sent from the Karaf - User mailing list archive at Nabble.com. > > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/OSGi-Compendium-within-a-feature-restarts-the-console-tp4045606p4045645.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
