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

Using javadoc.io for documentation #23

Open
vickumar1981 opened this issue Dec 3, 2018 · 0 comments
Open

Using javadoc.io for documentation #23

vickumar1981 opened this issue Dec 3, 2018 · 0 comments
Labels

Comments

@vickumar1981
Copy link
Owner

vickumar1981 commented Dec 3, 2018

Published maven artifacts, that contain documentation, can usually be found on javadoc.io.

For example, the same documentation hosted on the github.io page and linked from the README.md, can be found here as well, https://www.javadoc.io/doc/com.github.vickumar1981/stringdistance_2.12/1.0.7

Is javadoc.io a better location/main place to host the documentation and link to there from the README.md, or continue hosting on a github.io page?

Advantages of javadoc.io:

  • Relatively no maintenance, publishing the artifact updates the documentation.
  • Docs are automatically versioned, whereas on the github.io, you can only see the latest version of the docs.

Disadvantages of javadoc.io:

  • Maven central takes some time to sync. there's some delay between publishing an artifact, and it showing up on the search. even if it doesn't show up on the search doesn't mean it's not available, but it's the process is not instantaneous.

Advantages of using github.io page:

  • More control over when the documentation is updated. Can possibly tie the task to the travis build and automatically update documentation on any check-in to a snapshot or master branch.

Disadvantages of github.io page:

  • Need to maintain the documentation yourself.
  • Version of documentation always points to latest version of jar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant