[
https://issues.apache.org/jira/browse/LUCENE-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945911#comment-13945911
]
Shawn Heisey commented on LUCENE-5130:
--------------------------------------
After a couple of days, it's all starting to filter through and make sense.
Thanks for continuing to pound me with information, Uwe.
Is there any way with javac to pick and choose which warnings we want to simply
report and which ones we want to actually turn into errors? I suspect that the
answer to that question is "no."
> fail the build on compilation warnings
> --------------------------------------
>
> Key: LUCENE-5130
> URL: https://issues.apache.org/jira/browse/LUCENE-5130
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Fix For: 4.8
>
> Attachments: LUCENE-5130.patch, LUCENE-5130.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
