Failures to be fixed in

• Fix IBMSemeruTest for updated ChangeType wildcard import handling #1026

Analysis: What's needed for the two TODO items

1. @ManagedProperty name attribute removal

Problem: After the existing ChangeType migrates jakarta.faces.bean.ManagedProperty → jakarta.faces.annotation.ManagedProperty, the name attribute causes a compile error because Faces 4.0's @ManagedProperty doesn't have a name element.

Solution: The existing org.openrewrite.java.RemoveAnnotationAttribute recipe from rewrite-java core handles this — no custom Java code needed. Just add a YAML entry after the ChangeType steps:

- org.openrewrite.java.RemoveAnnotationAttribute:
    annotationType: jakarta.faces.annotation.ManagedProperty
    attributeName: name

Only the post-migration type (jakarta.faces.annotation.ManagedProperty) is needed since ChangeType runs first in the recipe list.

2. @CustomScoped migration

Problem: jakarta.faces.bean.CustomScoped was removed in Faces 4.0 with no direct replacement. The CDI equivalent involves defining a custom scope annotation with @NormalScope or @Scope, plus registering a Context implementation — this is NOT a simple ChangeType.

Status: This would require a custom Java recipe and the migration path isn't mechanical (the issue author also notes "unsure of recipe scope, and if feasible"). Skipping for now.

Thanks again! Does that removal through RemoveAnnotationAttribute make sense to you? Or would that lose something we still need to migrate?

Does that removal through RemoveAnnotationAttribute make sense to you? Or would that lose something we still need to migrate?

I have no personal experience with usage of these annotations, but it seems to make sense to me.
The current case is compilation error. And with removing the attribute, it seems the name is automatically based on the annotated field's name.