Support newer Jakarta Faces API versions (3.0, 4.0, 4.1)

[jansohn]

Would be great to get support for the newer Jakarta Faces API versions 3.0, 4.0 and 4.1 (see https://jakarta.ee/specifications/faces/). For now Eclipse seems to be stuck at version 2.3.

Related bugzilla reports:

• https://bugs.eclipse.org/bugs/show_bug.cgi?id=581893
• https://bugs.eclipse.org/bugs/show_bug.cgi?id=577596

[nitind]

Generally this requires contributors who understand the specifications and how to implement them in the JSF plug-ins. Those don't have to be the same people, though.

Other than adding the numbers, any idea what functionality has to be updated to work with the new package names? What new features in the specifications need to be supported in the existing functionality? What outright new functionality might even be good to add?

[himanshu-bectran]

@nitind , we need support especially for auto completion, code assist, and navigating to Java classes/methods when we click on an EL Expression in facelets.

I have posted a question in stack overflow, which can be viewed here.

[jansohn]

For us it is also mostly about code completion. I don't think there are any significant new features that would need to be exposed.

[bvfalcon]

In current moment migration to Jakarta Faces (without loss of functionality) is impossible: one of plugins -- Apache MyFaces Trinidad -- does not support Jakarta Faces specification.

I have made some modifications for support new JSF specifications (since Jakarta Faces 3.0), but support is not full: in several aspects current implementation is obsolete and it is easier to remove such aspects, than actualize them.
For example, documentation contains examples for JSF 1.2-2.0.) I am sure, such documentation should be removed.

[bvfalcon]

IMO, it still a lot of work with ensuring compatibility of changes with old JavaServer Faces versions (<= 2.3). But for some users support of old versions makes no sense. In such case update-site with changes can be used, that are already done.
Before PR #9 will be closed, update-site will be active. After closing update-site will be removed as unnecessary.