[ https://issues.apache.org/jira/browse/FELIX-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412461#comment-16412461 ]
Tuomas Kiviaho commented on FELIX-5794: --------------------------------------- Although there is a workaround to this in a form of a property, it seems that there is no directive variant (like {{-jpa-enable}}) available of it so the property will end up into the manifest. One way to circumvent this is of course to the plugin is all-together via {{<_disable-plugin>org.apache.felix.bundleplugin.JpaPlugin</_disable-plugin>}} but that can't be added to an external BND file {code:java} transformer.setParameter( "jpa-enable", analyzer.getProperty( "jpa-enable", "true" ) ); transformer.setParameter( "jpa-implementation", analyzer.getProperty( "jpa-implementation", "aries" ) ); transformer.setParameter( "jpa-datasource-req", analyzer.getProperty( "jpa-datasource-req", "true" ) ); {code} > maven-bundle-plugin fails to parse meta-persistence > --------------------------------------------------- > > Key: FELIX-5794 > URL: https://issues.apache.org/jira/browse/FELIX-5794 > Project: Felix > Issue Type: Bug > Components: Maven Bundle Plugin > Affects Versions: maven-bundle-plugin-3.4.0, maven-bundle-plugin-3.5.0 > Reporter: Jean-Baptiste Onofré > Priority: Major > > Since {{maven-bundle-plugin}} 3.4.0 (and the update to bnd 3.4.0), the plugin > fails to build bundle containing {{<Meta-Persistence/>}}. NB: the same bundle > builds fine with {{maven-bundle-plugin}} 3.3.0. > The cause is: > {code} > [INFO] --- maven-bundle-plugin:3.5.0:bundle (default-bundle) @ > karaf-jpa-example-provider --- > Output: [Provide-Capability: > osgi.service;effective:=active;objectClass=javax.persistence.EntityManager;osgi.unit.name="booking", > Provide-Capability: > osgi.service;effective:=active;objectClass=org.apache.aries.jpa.template.JpaTemplate;osgi.unit.name="booking", > Require-Capability: > osgi.service;effective:=active;objectClass=javax.sql.DataSource;filter:="(osgi.jndi.service.name=booking)", > DynamicImport-Package: org.hibernate.proxy;javassist.util.proxy, > Provide-Capability: > osgi.service;effective:=active;objectClass=javax.persistence.EntityManagerFactory;osgi.unit.name="booking", > Provide-Capability: > osgi.service;effective:=active;objectClass=org.apache.aries.jpa.supplier.EmSupplier;osgi.unit.name="booking", > Import-Package: > org.hibernate.proxy;javassist.util.proxy;resolution:=optional, > Require-Capability: osgi.extender;osgi.extender=aries.jpa, > Require-Capability: > osgi.service;effective:=active;objectClass=javax.persistence.spi.PersistenceProvider;javax.persistence.provider=org.hibernate.jpa.HibernatePersistenceProvider, > Require-Capability: > osgi.service;effective:=active;objectClass=javax.transaction.TransactionManager;] > [ERROR] Bundle > org.apache.karaf.examples:karaf-jpa-example-provider:bundle:4.2.0-SNAPSHOT : > Header contains name field after attribute or directive: null from > osgi.service;effective:=active;objectClass=javax.sql.DataSource;filter:="(osgi.jndi.service.name=booking)",osgi.extender;osgi.extender=aries.jpa,osgi.service;effective:=active;objectClass=javax.persistence.spi.PersistenceProvider;javax.persistence.provider=org.hibernate.jpa.HibernatePersistenceProvider,osgi.service;effective:=active;objectClass=javax.transaction.TransactionManager;. > Name fields must be consecutive, separated by a ';' like a;b;c;x=3;y=4 > [ERROR] Error(s) found in bundle configuration > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)