You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the landing page for the specifications at https://jakarta.ee/specifications is a little unwieldy. It lists all the Jakarta Specification projects in one big list, which I think sends the wrong message now when we try to make Jakarta EE a lean and mean platform.
Within the main list, without any marker, there are stable/pruned projects like:
Jakarta Deployment
Jakarta Management
Jakarta Web Services Metadata
Jakarta XML Registries
Jakarta XML RPC
Jakarta XML Web Services Specification
I feel these should go into a separate section of the page, under pruned/deprecated/stable projects.
Next, the page would look much better if the specs listed were organised under
(Full) platform, Web Profile, Core Profile and Standalone/candidates.
Currently the landing page for the specifications at https://jakarta.ee/specifications is a little unwieldy. It lists all the Jakarta Specification projects in one big list, which I think sends the wrong message now when we try to make Jakarta EE a lean and mean platform.
Within the main list, without any marker, there are stable/pruned projects like:
I feel these should go into a separate section of the page, under pruned/deprecated/stable projects.
Next, the page would look much better if the specs listed were organised under
(Full) platform, Web Profile, Core Profile and Standalone/candidates.
CC @ivargrimstad
The text was updated successfully, but these errors were encountered: