-
Notifications
You must be signed in to change notification settings - Fork 97
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
Adds javadoc generator test #1182
Conversation
Test passed somehow, not needed anymore
@@ -504,6 +504,11 @@ java-examples: | |||
cd $(SWIFTNAV_ROOT)/java/example && gradle clean fatjar | |||
$(call announce-end,"Finished building fat jar") | |||
|
|||
javadoc javadocs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could make the dependency of the Java
target so that it runs locally-- would there be any downsides to that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As in - instead of the additional workflow we just add make javadocs
to make java
or make test-java
when it is locally ran?
Not sure if the make javadocs
is necessary overall - just to verify whether there are any errors preventing javadocs built when publishing i.e. #1180 probably not needed since errors should rarely occur(?) so can probably close this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If errors are rare then this is a good place to verify, making everyone check it locally sounds unnecessary
Description
Checks whether javadocs can be built successfully to prevent gradle errors
JIRA Reference
https://swift-nav.atlassian.net/browse/DEVINFRA-807