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

Fixed doc typos re: @Jsonb(De)Serializer #183

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mkarg
Copy link
Contributor

@mkarg mkarg commented Aug 21, 2019

Partial fix of #70 (JavaDocs only)

Unfortunately I could only fix the JavaDocs, as there is just boilerplate for the actual spec.

@mkarg
Copy link
Contributor Author

mkarg commented Aug 21, 2019

I marked this PR as a draft, as the spec source is not contained. Please tell me if I shall keep it in draft state until the spec source is available, or whether I shall turn it in a real PR so you could merge it. Thanks. :-)

@aguibert
Copy link
Contributor

hi @mkarg thanks for the PR! I agree it would be good to update the spec doc at the same time as the javadoc so we don't lose track and the spec and javadoc become inconsistent with each other.

@m0mus do we have an ETA on when the real spec doc will be available on this repo?

@aguibert aguibert added the documentation Involves the spec or javadocs label Aug 27, 2019
@m0mus
Copy link
Contributor

m0mus commented Aug 27, 2019

@aguibert You better ask Eclipse folks. They need to do some legal checks before allowing us using the old spec text.

@mkarg
Copy link
Contributor Author

mkarg commented Aug 27, 2019

@m0mus Did EF already ask you for your approval of the spec? I was asked weeks ago and it seems nothing happend so far.

So how to proceed? Keep the PR in draft state until we have the OK from the EF, or merge this PR, keep the issue open, and create another PR for the spec change?

@m0mus
Copy link
Contributor

m0mus commented Aug 28, 2019

@mkarg No, I didn't have any request from EF regarding the spec. I suppose that it will happen after Jakarta EE 8 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Involves the spec or javadocs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants