You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "hudi-bot (via GitHub)" <gi...@apache.org> on 2025/11/30 03:35:15 UTC
[I] Clean up all warnings during compilation [hudi]
hudi-bot opened a new issue, #14661:
URL: https://github.com/apache/hudi/issues/14661
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-1242
- Type: Improvement
- Epic: https://issues.apache.org/jira/browse/HUDI-2261
- Affects version(s):
- 0.9.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Clean up all warnings during compilation [hudi]
Posted by "deepakpanda93 (via GitHub)" <gi...@apache.org>.
deepakpanda93 commented on issue #14661:
URL: https://github.com/apache/hudi/issues/14661#issuecomment-5281482325
This issue was reviewed as part of the JIRA-migrated backlog triage. Original report is >4 years old (last activity 2022-05-09) with no description beyond the title, and no repro or acceptance criteria.
For the record, this is not simply unattended - as written it is not achievable, because nothing in the build enforces it:
- `maven-compiler-plugin` (`pom.xml:380-400`) configures only `source`, `target` and the Lombok annotation-processor path. There is no `-Werror`, `-Xlint`, `showWarnings`, `showDeprecation` or `-nowarn`.
- `scala-maven-plugin` passes only `-nobootcp` (plus a genjavadoc arg in one profile) - no `-deprecation`, `-feature` or `-unchecked`.
- Repo-wide, `-Xlint` has no hits at all.
With no gate, warnings are neither counted nor prevented, so any one-off cleanup would regress immediately and invisibly. "Clean up all warnings" also names no target warning set, module or policy.
Closing as stale. If this is still wanted, a scoped and enforceable version would be much more likely to land - for example: enable `-Xlint:all` for one module, fix that module's warnings, then add `-Werror` for that module so regressions fail the build. That is a ticket someone can finish.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Clean up all warnings during compilation [hudi]
Posted by "deepakpanda93 (via GitHub)" <gi...@apache.org>.
deepakpanda93 closed issue #14661: Clean up all warnings during compilation
URL: https://github.com/apache/hudi/issues/14661
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org