fail the build on compilation warnings [LUCENE-5130]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Many modules compile w/o warnings ... we should lock this in and fail the build if warnings are ever added, and try to fix the warnings in existing modules.
---
Migrated from [LUCENE-5130](https://issues.apache.org/jira/browse/LUCENE-5130) by Michael McCandless (@mikemccand), updated May 09 2016
Attachments: [LUCENE-5130.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-5130/LUCENE-5130.patch) (versions: 2)
Linked issues:
- #6613
Contributor guide
Research direction
Review the issue description and the attached LUCENE-5130.patch first; no source files, tests, or build entry points are identified in the payload. Done means the build fails when compilation warnings are introduced and existing warnings in modules are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100