Closed ops4j-issues closed 8 years ago
Guillaume Nodet commented
Could you double-check with the following patch instead :
diff --git a/pax-cdi-parent/pom.xml b/pax-cdi-parent/pom.xml
index 788f61f..fa3cc25 100644
--- a/pax-cdi-parent/pom.xml
+++ b/pax-cdi-parent/pom.xml
@@ -352,6 +352,7 @@
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
+ <version>3.0.1</version>
<extensions>true</extensions>
<configuration>
<unpackBundle>true</unpackBundle>
John Poth created PAXCDI-226
pax-cdi-extender correctly declares the following requirement in it's MANIFEST:
Require-Capability: ...,osgi.service;effective:=active;filter:="(objectClass=javax.ent
erprise.inject.spi.CDIProvider)"
But it is also the provider of that requirement and fails to declare it in it's MANIFEST.
This causes the following error when installing the new pax-cdi-weld feature in FUSE:
This also causes any feature depending on pax-cdi-weld to fail (e.g switchyard-bean).
Affects: 1.0.0.RC1 Fixed in: 1.0.0.RC2 Votes: 0, Watches: 2