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

Generated docs are sometimes overridden when running full build #5097

Closed
machi1990 opened this issue Oct 31, 2019 · 0 comments · Fixed by #5044
Closed

Generated docs are sometimes overridden when running full build #5097

machi1990 opened this issue Oct 31, 2019 · 0 comments · Fixed by #5044
Assignees
Labels
area/documentation kind/bug Something isn't working
Milestone

Comments

@machi1990
Copy link
Member

Describe the bug
When running a full build, we sometimes override a previous part of a generated doc

Expected behavior
We should merge extensions doc and not overriding a partial or fully generated one

Actual behavior
Docs are overridden - e.g when running a full build, the quarkus-vertx-http.adoc generated doc does not contain all the information about http configuration.

But when build the vertx-http extension alone, the file in question contains all the information.

Environment (please complete the following information):

  • Quarkus version or git rev: problem observed in latest master 9ed6438

Additional context
I'll come up with a fix, still investigating on ways to work around this.

@machi1990 machi1990 added kind/bug Something isn't working area/documentation labels Oct 31, 2019
@machi1990 machi1990 self-assigned this Oct 31, 2019
@gsmet gsmet added this to the 0.28.0 milestone Nov 3, 2019
@gsmet gsmet changed the title generated docs are sometimes overridden when running full build Generated docs are sometimes overridden when running full build Nov 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants