JakartaEE: Fix more cases where jakarta namespace has to be supported #6473
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NetBeans has partitial support for JakartaEE 9+, but several areas that provide support are still lacking support for the new package namespace "jakarta." instead of "javax.".
This PR adjusts a subset of these cases and focuses on the JPA and JSF area. Further areas where identified while working on this and were marked with @todo comments.
There are two areas, that form the main picture: Code generated in the wrong package namespace and code scanning not finding classes in the new "jakarta" namespace. For the former switches were introduced, that change the generated code to the "jakarta" namespace when a compatible JSF version is detected. The code scanning was in most placed adjusted, so that both variants "javax" and "jakarta" are recognized.
Closes: #6445
Closes: #4840