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

move the current source to an api submodule and introduce tck and spec modules #21

Closed
struberg opened this issue Jan 18, 2017 · 1 comment
Milestone

Comments

@struberg
Copy link
Contributor

At the end we need 3 submodules in our repo

  • api (simply move the current project root into this sub-module)
  • tck (the Microprofile-config TCK)
  • spec (the asciidoc based spec PDF/html/etc)
struberg added a commit to struberg/microprofile-config that referenced this issue Jan 18, 2017
That will allow to also keep the spec and tck modules in the same repository.
struberg added a commit to struberg/microprofile-config that referenced this issue Jan 18, 2017
WORK IN PROGRESS!

* The wording of the spec paper still uses the wording of the original proposal
* We need to introduce ConfigProvider#registerConfig for Gunnar
* I have actually many more TCK tests which need to get imported still.
struberg added a commit to struberg/microprofile-config that referenced this issue Jan 18, 2017
struberg added a commit that referenced this issue Jan 18, 2017
@struberg
Copy link
Contributor Author

Imported the structure and initial data.
This still needs adoption to the current API version and likely discuss or remove a few features which are not yet in our API (e.g. dynamic reload of configured value which might change at runtime)

@struberg struberg modified the milestone: config-1.0 Mar 10, 2017
Emily-Jiang added a commit that referenced this issue Mar 16, 2017
…dinal is the same

Signed-off-by: Emily Jiang <emijiang6@googlemail.com>
Emily-Jiang added a commit that referenced this issue Mar 16, 2017
#21 change javadoc on ordering config sources to use configname if or…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant