The jar is actually there if you search for ‘osgi:org.osgi.service.jdbc’. (p: is package, osgi: symbolic name, a: artifact id, g: group id).
PAX JDBC has wrapped it in http://repo1.maven.org/maven2/org/ops4j/pax/jdbc/pax-jdbc-spec/0.5.0/pax-jdbc-spec-0.5.0.jar and given it the same Bundle Symbolic name as OSGi has (org.osgi.service.jdbc). You can see the different revisions here, it mixes OSGi & PAX: http://jpm4j.org/#!/p/org.ops4j.pax.jdbc/pax-jdbc-spec?tab=history <http://jpm4j.org/#!/p/org.ops4j.pax.jdbc/pax-jdbc-spec?tab=history> JPM seems to got confused with this and added the OSGi jar the PAX group. The correct revision is here: http://jpm4j.org/#!/p/sha/C6700A43B970431774A6C2FF73A35C5F9AB0D0D8//0.0.0 <http://jpm4j.org/#!/p/sha/C6700A43B970431774A6C2FF73A35C5F9AB0D0D8//0.0.0> You can add any bundle by logging in, clicking on your email address right top, and then go to the Actions tab. Add a URL to an index.xml or JAR and it should import the JARs. Make sure you set the popup on MASTER. You might want to report a bug or PR on PAX for another symbolic name. Kind regards, Peter Kriens > On 9 jun. 2016, at 23:44, Paul F Fraser <pa...@a2zliving.com> wrote: > > Hi, > > Signed up on JPM4j site, logged in, but could not find how to introduce new > jar. > > Anyone advise if possible and how. > > I want to add or find org.osgi.service.jdbc > > Paul > > > > On 10/06/2016 2:26 AM, Raymond Auge wrote: >> ... at least that's what I understood from how I fixed the portlet artifacts >> in jpm4j several months ago ... >> >> - Ray >> >> On Thu, Jun 9, 2016 at 12:24 PM, Raymond Auge <raymond.a...@liferay.com >> <mailto:raymond.a...@liferay.com>> wrote: >> 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 < >> <mailto:ch...@die-schneider.net>ch...@die-schneider.net >> <mailto: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 Schneider >> http://www.liquid-reality.de <http://www.liquid-reality.de/> >> >> Open Source Architect >> http://www.talend.com <http://www.talend.com/> >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> <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) >> >> >> >> -- >> 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 <mailto:osgi-dev@mail.osgi.org> >> https://mail.osgi.org/mailman/listinfo/osgi-dev >> <https://mail.osgi.org/mailman/listinfo/osgi-dev> > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
