Open Azquelt opened 7 months ago
This looks like an oversight to me.
Definitely an oversight, both JARs need that dep for the exact same method on BM (which we kept in CDI API because of backwards compatibility) so there is no reason for them to differentiate.
Describe the bug
For a package import, the version is a range and so
5.0
here means "5.0
or above" so both ranges do allow version 6.0 to be used.Expected behavior I had expected the two jars to match. There may be some reason I'm not aware of for doing it this way, or it could be an oversight.