karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (Jira) <j...@apache.org>
Subject [jira] [Commented] (KARAF-6573) Not able to add jdbc feature in a static distribution
Date Sun, 05 Jan 2020 16:12:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008345#comment-17008345
] 

Jean-Baptiste Onofré commented on KARAF-6573:
---------------------------------------------

I think I found the problem. When using PAX JDBC (for instance via the {{jdbc}} feature) in
a static distribution, I got:
{code:java}
[ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.2.8-SNAPSHOT:assembly
(process-resources) on project static-jdbc-distro: Unable to build assembly: Unable to resolve
root: missing requirement [root] osgi.identity; osgi.identity=pax-jdbc; type=karaf.feature;
version=0; filter:="(&(osgi.identity=pax-jdbc)(type=karaf.feature)(version>=0.0.0))"
[caused by: Unable to resolve pax-jdbc/1.4.0: missing requirement [pax-jdbc/1.4.0] osgi.identity;
osgi.identity=org.ops4j.pax.jdbc; type=osgi.bundle; version="[1.4.0,1.4.0]"; resolution:=mandatory
[caused by: Unable to resolve org.ops4j.pax.jdbc/1.4.0: missing requirement [org.ops4j.pax.jdbc/1.4.0]
osgi.wiring.package; filter:="(&(osgi.wiring.package=org.slf4j)(version>=1.6.0)(!(version>=2.0.0)))"]]
{code}

> Not able to add jdbc feature in a static distribution
> -----------------------------------------------------
>
>                 Key: KARAF-6573
>                 URL: https://issues.apache.org/jira/browse/KARAF-6573
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 4.3.0, 4.2.8
>
>
> An user reported issues to include jdbc feature in a Karaf static distribution. I will
test that and eventually fix.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message