Open ops4j-issues opened 8 years ago
Marc Schlegel commented
Could you try to move the startorder from all cdi-related bundles to a later stage (after gemini)?
I´ve recently played with pax-cdi myself and had similar issues which where solved by using the right start-order. In my case pax-web has to be started before pax-cdi.
P created PAXCDI-223
I have a bundle which works with eclipselink via eclipse gemini (? - that's why the problem is also discussed at gemini forum - https://www.eclipse.org/forums/index.php/m/1733050/ ) Although I am not sure that the problem in this. However, the exception occurs only when I add META-INF/beans.bnd to manifest of the jar.
The content of beans.bnd:
The list of bundles I install:
The exception which I get:
Affects: 1.0.0.RC1 Votes: 0, Watches: 2