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

[Bug]: Reference of spark and java in website is missing #268

Closed
1 task done
Thespica opened this issue Oct 31, 2023 · 1 comment · Fixed by #269
Closed
1 task done

[Bug]: Reference of spark and java in website is missing #268

Thespica opened this issue Oct 31, 2023 · 1 comment · Fixed by #269
Assignees
Labels
bug Something isn't working

Comments

@Thespica
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

As titile.

Expected Behavior

displaying scaladoc and javadoc

Minimal Reproducible Example

image
image

Environment

  • Operating system:
  • GraphAr version:

Link to GraphAr Logs

No response

Further Information

scala: invalid output arguments -DoutputDirectory. Keep original way to generate docs.

java: use whitespace rather than tab in makefile, which may leads problems.

@acezen
Copy link
Contributor

acezen commented Oct 31, 2023

refer to html generate process: https://github.com/alibaba/GraphAr/blob/c752915bb4a8842423d91481def089e873712b7d/docs/Makefile#L53-L57

seems that the process generate api-doc of c++/java/spark before SPHINXBUILD, so the _build/html directory is not existed yet in api-doc process, and failed to generate to the directory.

The better solution is make html generate process build SPHINXBUILD first and then build the api-doc document.

@acezen acezen added the bug Something isn't working label Oct 31, 2023
@acezen acezen added this to the Release v0.10.0 [In Progress] milestone Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants