-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change CMP/BMP tests to be optional via unique keyword (or profile) #742
Comments
Note that
|
It looks like the EJB Lite feature is already optional via https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/install/jakartaee/other/vehicle.properties#L140: As well as https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/install/jakartaee/other/vehicle.properties#L156 for ejb32/lite and https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/install/jakartaee/other/vehicle.properties#L164 for ejb32/timer |
Removing the |
Confirming that the CMP/BMP tests should have already been optional. Similarly, the embedded EJB container was made optional in Java EE 7. Short of removing the tests, there shouldn't be anything to do. We'd need to establish a separate EJB TCK before we could actually remove any tests as these APIs are still implemented and shipped as addons/additional features/additional specs supported. |
Note: There are 16 test packages that contain some tests that require entity beans alongside others that do not. Some work could conceivably be done to divide these packages so vendors that don't support entity beans had the ability to run and report these tests.
|
@dblevins should we discuss #947 on [email protected] and whether the proposed change should be included for EE 10 or after EE 10? |
As per https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee10/JakartaEE10ReleasePlan, Jakarta Enterprise Beans tests that use entity beans (CMP and BMP) need to be be optional via unique keywords (or profiles). Note that the release plan also mentions these tests may need to be removed instead (depending on outcome of EclipseFdn/EFSP#22).
The text was updated successfully, but these errors were encountered: