[
https://issues.apache.org/jira/browse/LUCENE-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940979#comment-13940979
]
Uwe Schindler edited comment on LUCENE-5130 at 3/19/14 9:01 PM:
----------------------------------------------------------------
Hi,
one important thing: We should *not* use something like "+all warning -some
warnings". In that case we would prevent later java versions with more possible
warnings (covered by +all) from suceeding the build. Failing on warnings should
be done with an explicit set of warnings given. This is just a warning about
the warnings :-)
was (Author: thetaphi):
Hi,
one important thing: We should i*not* use something like "+all warning -some
warnings". In that case we would prevent later java versions with more possible
warnings (covered by +all) from suceeding the build. Failing on warnings should
be done with an explicit set of warnings given. This is just a warning about
the warnings :-)
> 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]
