-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-26093 Deduplicate org.apache.hadoop.hive.metastore.annotation package-info.java #3168
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
Conversation
|
@zabetak: Could you please take a look?
We still should fix the javadoc issues, but at least in the meantime we have a way to generate the javadoc |
zabetak
left a comment
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.
I had a quick look and left some small questions.
| <plugins> | ||
| <plugin> | ||
| <groupId>org.apache.maven.plugins</groupId> | ||
| <artifactId>maven-javadoc-plugin</artifactId> |
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.
I think we should also fix the version of the maven-javadoc-plugin globally to avoid build warnings and things being broken when a newer version appears.
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.
Since the javadoc generation is a big mess ATM, I would suggest to keep it as it is, and if the tests are failing then we can decide what we want to do with them.
See also: #3185
…ckage-info.java (Peter Vary reviewed by Stamatis Zampetakis) (apache#3168)
…ckage-info.java (Peter Vary reviewed by Stamatis Zampetakis) (apache#3168)
What changes were proposed in this pull request?
Remove the source generation for org/apache/hadoop/hive.metastore/annotation/package-info.java
Why are the changes needed?
Javadoc generation failed during the release process
Does this PR introduce any user-facing change?
No
How was this patch tested?
Generating javadoc