Skip to content
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

How to handle optional features in Specifications #54

Closed
paulbuck opened this issue Jun 21, 2022 · 6 comments
Closed

How to handle optional features in Specifications #54

paulbuck opened this issue Jun 21, 2022 · 6 comments
Labels
enhancement New feature or request

Comments

@paulbuck
Copy link

General discussions occurred at previous Spec Committee calls:
From July 14th, 2021 - For background see proposal from Dan, Kevin & Scott

For Jakarta EE 10 a resolution was passed:
From August 25th, 2021 - See ballot results for the “RESOLUTION: The Jakarta EE Specification Committee resolves that no new optional features may be added in Jakarta EE 10 and beyond in component, Platform, or Profile specifications.

@paulbuck paulbuck added the enhancement New feature or request label Jun 21, 2022
@paulbuck
Copy link
Author

  1. An individual specification can have optional features, however when a component specification is included in the Platform an optional feature must be declared required (or included), or it is not included. This requirement to be noted in the Platform specification.
  2. Also note, in Jakarta EE 10, the Platform project's intention was to remove all the then existing optional features. This was apparently not reflected in the EE 10 Platform specification.
    If 1. is adopted, 2. is no longer needed. The guidance in the 08/25/21 resolution would need to be revised to include optional features in component specifications.
    There are impacts to compatibility that need to be carefully considered.
    Discussion to be continued.

@dblevins
Copy link
Collaborator

Item to add to the discussion, in the Core Profile specification there is a section dedicated to specifications which are optional and features of specifications which are optional.

This seems to contradict the August 25th, 2021 resolution. That section uses the word optional and also uses words from the dictionary definition of optional, which is "left to one's choice; not required or mandatory:"

@paulbuck
Copy link
Author

Revise 1. to .... "An individual specification can have optional features, however when a component specification is included in the Platform Web and Core Profiles an optional feature must be declared required (or included), or it is not included. This requirement to be noted in the Platform specification." and consider putting forward as a resolution to vote on.

@paulbuck
Copy link
Author

Draft resolution to be voted on the 02/08/23 call: "An individual specification can have optional features, however when a component specification is included in the Platform and Web Profile, and Core Profile an optional feature must be explicitly declared as required, otherwise it is not required. This requirement to be noted in the Platform specification."

@edburns
Copy link

edburns commented Aug 9, 2023

@ivargrimstad can you please add label jea-linked to this issue? I'd like to be able to add labels, but I cannot. Linked to AB#101

@edburns
Copy link

edburns commented Feb 22, 2024

This really should be closed, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants