jpm4j doesn't know on it's own what is the most relevant artifact to use. I believe it will assume that the artifact with the most recent release date is most relevant.
However, we can teach jpm4j how to behave (because it's impossible for jmp4j to figure this out on it's own... although it tries really hard). You can login to the jpm4j website and if you are a connoisseur of the API in question, you can mark a particular artifact as being more relevant. In this case you could mark org.osgi.service.jdbc more relevant than org.ops4j.pax.jdbc and when the resolve query involves the packages which are the same, jpm will return the most relevant one first. HTH, - Ray On Thu, Jun 9, 2016 at 7:46 AM, Christian Schneider <ch...@die-schneider.net > wrote: > Please use the original one. org.ops4j.pax.jdbc contains more than the > spec bundle. > The new pax-jdbc releases do not embed the jdbc spec bundle anymore. > Instead it also uses > the one from the OSGi alliance I mentioned. > > Btw. Strange that jpm does not find the official one. > > Christian > > On 09.06.2016 13:27, Paul F Fraser wrote: > > Thanks, Christian, > > JPM finds org.ops4j.pax.jdbc but search in Maven finds > org.osgi.service.jdbc. > I presume both are suitable. > > Paul > > > -- > Christian Schneiderhttp://www.liquid-reality.de > > Open Source Architecthttp://www.talend.com > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
