lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3850) Fix rawtypes warnings for Java 7 compiler
Date Thu, 08 Mar 2012 17:13:58 GMT


Uwe Schindler commented on LUCENE-3850:

bq. warning: [options] bootstrap class path not set in conjunction with -source 1.6

Its because you are compiling the code with Java 7 but using 1.6 compatibility. Previous versions
did not complain about that (e.g. compiling 1.5 code with 1.6). This warning simply says,
that you should have a different bootstrap classpath with only the 1.6 JDK rt.jar in it, so
the compiler can check that the methods/classes you are using are really existing. If you
compoile against Java 7's rt.jar this is not guaranteed.

The warning is obsolete for us, as we also check java 6 and java 5 (for 3.x).
> Fix rawtypes warnings for Java 7 compiler
> -----------------------------------------
>                 Key: LUCENE-3850
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>    Affects Versions: 3.5, 4.0
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>             Fix For: 3.6, 4.0
>         Attachments: LUCENE-3850-part1-branch3x.patch, LUCENE-3850-part1.patch, LUCENE-3850-part2.patch,
> Java 7 changed the warnings a little bit:
> - Java 6 only knew "unchecked" warning type, applying for all types of generics violations,
like missing generics (raw types)
> - Java 7 still knows "unchecked" but only emits warning if the call is really unchecked.
Declaration of variables/fields or constructing instances without type param now emits "rawtypes"
> The changes above causes the Java 7 compile now emit lots of "rawtypes" warnings, where
Java 6 is silent. The easy fix is to suppres both warning types: @SuppressWarnings({"unchecked","rawtypes"})
for all those places. Changes are easy to do, will provide patch later!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message