Prepare compatibility with CDI 2.0 runtime [PAXCDI-222]

[ops4j-issues]

Antonin Stefanutti created PAXCDI-222

CDI 2.0 specification is under development. Given the backward-compatibility guarantee provided by the API, the package import range can be extended to support CDI 2.0 as well as major implementation versions.

---

Fixed in: 1.1.4
Votes: 1, Watches: 3

[ops4j-issues]

Harald Wellmann commented

I see your point, but just extending the import ranges is necessary but not sufficient to make things work.

Is this just an academic proposal, or have you tried using Weld 3.x? If it does work, then you should arrange for the entire integration suite to run on Weld 3, in addition to Weld 2.

Without any tests, any compatibility declaration is a shallow promise.

[ops4j-issues]

Antonin Stefanutti commented

I've tested it extensively on Camel CDI: https://github.com/astefanutti/camel-cdi/tree/cdi-2.0/envs/osgi/src/test.

[ops4j-issues]

Jean-Baptiste Onofre commented

I think it’s fair to just update the range as a first step. It’s not a strong guarantee but a step forward.