-
Notifications
You must be signed in to change notification settings - Fork 112
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
Remove jakarta.annotation.managedbean tests from Platform TCK #1184
Comments
Hello @scottmarlow , can you please create a label "jea-linked" with color |
@edburns done via
jea-linked
|
Please confirm this sketch for how a new helper could complete the task.
Also, please confirm the changes for this issue should be made to the master branch of https://github.com/jakartaee/platform-tck . |
…otation-api from 2.1.1 to 3.0.0 (jakartaee#1467)" until we address jakartaee#1184 This reverts commit dfa720a.
At the moment we still seem to have 5 hits for "@ManagedBean" in the project. |
I see 3 in my local copy, and a lot of it is weird to me.
The source tree that I did the 1558 changes from didn't even have a I'll also point out that I had this note in my PR: Note: This does leave behind one awkward test in ejb30/lite/packaging/war/mbean/interceptor/lifecycleejbcdi, which despite the location is not actually a ManagedBean test in any way. Despite that, it looks like -- The other one I see is :
That one was converted to a CDI bean in my PR, but that change was apparently lost when the JMS tests were transformed, -- What are the other two you're seeing? |
In support of jakartaee/common-annotations-api#115 remove jakarta.annotation.managedbean Platform TCK tests.
Work is to be done on https://github.com/jakartaee/platform-tck/tree/tckrefactor
The above tests need to be removed or updated to not reference
jakarta.annotation.ManagedBean
.The text was updated successfully, but these errors were encountered: