Introduction draft #147
Open
Introduction draft #147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dmitry Kornilov <[email protected]>
Emily-Jiang
reviewed
Feb 9, 2023
|
|
||
| === Resources | ||
|
|
||
| - GitHub repository: https://github.com/eclipse-ee4j/config |
There was a problem hiding this comment.
I am not sure we want to include this. I have not seen other spec mention this. Besides the location might change.
There was a problem hiding this comment.
I suggest to put this info in the readme instead of the spec itself.
Emily-Jiang
reviewed
Feb 9, 2023
|
|
||
| Jakarta Config ("Specification") is a Java API for working with configurations. It supports externalized configuration allowing applications to use different configurations for different environments (dev, test, prod), and allows reading data from different layered configuration sources such as property files, environment variables, etc. | ||
|
|
||
| === Goals |
There was a problem hiding this comment.
I suggest to put these in the readme instead of the spec doc as it is more suitable there.
ljnelson
reviewed
Feb 10, 2023
| - Specification must provide integration with CDI and optionally with dependency injection frameworks. | ||
| - Specification must distinguish empty strings and null values. | ||
| - Specification must support profiles such as dev, test and prod. | ||
| - Specification must support both mutable and immutable configuration sources. |
There was a problem hiding this comment.
It would seem we have agreed otherwise: #109
ljnelson
reviewed
Feb 10, 2023
|
|
||
| === Scope | ||
|
|
||
| Jakarta Config ("Specification") is a Java API for working with configurations. It supports externalized configuration allowing applications to use different configurations for different environments (dev, test, prod), and allows reading data from different layered configuration sources such as property files, environment variables, etc. |
There was a problem hiding this comment.
I understand this is just a sketch. As it exists, it needs a lot of work. I will try to draft an introduction befitting a Jakarta EE specification. I will look at our discussion in #142 to proceed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.