karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Chapman (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-6179) pax-jdbc-mysql feature missing
Date Fri, 01 Mar 2019 04:03:00 GMT
Steve Chapman created KARAF-6179:
------------------------------------

             Summary: pax-jdbc-mysql feature missing
                 Key: KARAF-6179
                 URL: https://issues.apache.org/jira/browse/KARAF-6179
             Project: Karaf
          Issue Type: Bug
          Components: karaf
    Affects Versions: 4.2.3
            Reporter: Steve Chapman


I have created a Karaf distribution using the karaf.maven.plugin specifying bootfeature config
including pax-jdbc, pax-jdbc-config and pax-jdbc-mysql.

It builds and starts without issue. 

When I deploy a kar/feature into the generated karaf with a feature dependency of pax-jdbc-mysql
I find that my module does not start because of missing feature pax-jdbc-mysql.

>From the karaf console - 'feature:list | grep jdbc' does not show any pax-jdbc-mysql feature.

When I look in the pax-jdbc-features.xml e.g. 
 http://localhost:8081/repository/maven-public/org/ops4j/pax/jdbc/pax-jdbc-features/1.3.4/pax-jdbc-features-1.3.4-features.xml

... I can see that mysql is not in the list of jdbc drivers. 

It appears that it was dropped from pax-jdbc-features.xml since version 1.2.1.

I therefore needed to add the feature dependency myself by including the pax-jdbc-mysql feature
in my kar module's feature.xml, e.g. 


{code:xml}
 	<feature name="pax-jdbc-mysql"
		description="Provides JDBC MySQL DataSourceFactory" version="1.3.4">
		<feature>pax-jdbc-spec</feature>
		<bundle dependency="true">mvn:mysql/mysql-connector-java/5.1.47</bundle>
		<bundle>mvn:org.ops4j.pax.jdbc/pax-jdbc-mysql/1.3.4</bundle>
	</feature>
{code}

The current Karaf documentation indicates that pax-jdbc-mysql will be available. MySQL is
a commonly used database so I am sure others will have the same issue. Perhaps the Karaf documentation
needs to identify this issue and provide a workaround like the one I have used. 




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message