You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update to 3.1.7.Final was reported broken for mybatis-cdi private usage.
This can be demonstrated in our current test set. Simply bump cdi 2.0 support weld up to 3.1.7.Final and run the build with cdi 2.0 profile.
mvn clean install -P"cdi-2.0"
[INFO] Running org.mybatis.cdi.FooServiceTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.107 s <<< FAILURE! - in org.mybatis.cdi.FooServiceTest
[ERROR] org.mybatis.cdi.FooServiceTest Time elapsed: 0.107 s <<< ERROR!
I believe this has to do with the proxy and use of interfaces. I haven't done any further research yet and this could be a bug with weld itself given they broke this on a patch level.
The text was updated successfully, but these errors were encountered:
Update to 3.1.7.Final was reported broken for mybatis-cdi private usage.
This can be demonstrated in our current test set. Simply bump cdi 2.0 support weld up to 3.1.7.Final and run the build with cdi 2.0 profile.
mvn clean install -P"cdi-2.0"
[INFO] Running org.mybatis.cdi.FooServiceTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.107 s <<< FAILURE! - in org.mybatis.cdi.FooServiceTest
[ERROR] org.mybatis.cdi.FooServiceTest Time elapsed: 0.107 s <<< ERROR!
I believe this has to do with the proxy and use of interfaces. I haven't done any further research yet and this could be a bug with weld itself given they broke this on a patch level.
The text was updated successfully, but these errors were encountered: