[msbuild] JavaDocJar items should also be passed to ClassParse task. #437
Conversation
This file contains hidden or 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
ClassParse implementation actually ignores the doclet types so this change itself actually doesn't do anything (changes to Java.Interop is being published too). So far it passes new jar-originated docs just like other JavaDoc/DroidDoc properties.
Contributor
Author
|
Related: dotnet/java-interop#125 (ClassParse fix to actually implement doclet type detection) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
ClassParse implementation actually ignores the doclet types so this change
itself actually doesn't do anything (changes to Java.Interop is being
published too). So far it passes new jar-originated docs just like other
JavaDoc/DroidDoc properties.