cleanup scaladoc #42
Merged
cleanup scaladoc #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fixed various issues in the scaladoc to remove all but two of the scaladoc warnings. The last two unresolved warnings relate to linking to external scaladoc / javadoc. I could not figure out how to get scaladoc to link to external documents without using absolute urls. Will make this a separate issue in case we want to pursue this.
clinedome-work
added a commit
that referenced
this pull request
Feb 28, 2014
cleanup scaladoc Ignoring build failure, it had nothing to do with this patchset and was addressed in a separate commit.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixed various issues in the scaladoc to remove all but two of the
scaladoc warnings. The last two unresolved warnings relate to
linking to external scaladoc / javadoc. I could not figure out how to
get scaladoc to link to external documents without using absolute
urls. Will make this a separate issue in case we want to pursue this.
see related issue #41