Skip to content

Javadoc fail on warning during CI build#613

Merged
bitwiseman merged 2 commits into
hub4j:masterfrom
bitwiseman:javadoc-warning
Nov 14, 2019
Merged

Javadoc fail on warning during CI build#613
bitwiseman merged 2 commits into
hub4j:masterfrom
bitwiseman:javadoc-warning

Conversation

@bitwiseman
Copy link
Copy Markdown
Member

Description

Added failOnWarning and "fixed" all existing warnings. The fix was to auto-populate them, but something is better than improperly formatted entries.

Before submitting a PR:

We love getting PRs, but we hate asking people for the same basic changes every time.

  • Push your changes to a branch other than master. Create your PR from that branch.
  • Add JavaDocs and other comments
  • Write tests that run and pass in CI. See CONTRIBUTING.md for details on how to capture snapshot data.
  • Run mvn install site locally. This may reformat your code, commit those changes. If this command doesn't succeed, your change will not pass CI.

Do using IntelliJ JavaDocs plugin. Better to have something than nothing.
Continuing to ratchet up some base level code quality
@bitwiseman bitwiseman merged commit d3564a9 into hub4j:master Nov 14, 2019
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

Successfully merging this pull request may close these issues.

1 participant