sdk/settings, branch replicant-6.0 sdk Change Eclipse compiler errors for null issues to warnings 2013-06-12T17:03:02+00:00 Tor Norbye tnorbye@google.com 2013-06-12T17:03:02+00:00 85108119976f74a36a26b87569459ebaa28b01bd Change-Id: I6cd127ed7034ba33c32a1994bc312e187a15b250 
Change-Id: I6cd127ed7034ba33c32a1994bc312e187a15b250
Update compiler flags. 2012-10-26T15:21:09+00:00 Tor Norbye tnorbye@google.com 2012-10-26T15:21:09+00:00 1c811c9bbfd08e511ccd95cddbee5f6b857f4d3e Turns off the ability to use @SuppressWarnings with optional errors is available, but off by default (see Eclipse issue 392875). This turns that off, makes missing enums in switch statements a warning, and synchronizes the settings file to all projects (except tests.) Change-Id: Iad7060523b6ee2cbbca97e0a6ffedb264b185222 
Turns off the ability to use @SuppressWarnings with optional
errors is available, but off by default (see Eclipse issue 392875).
This turns that off, makes missing enums in switch statements a
warning, and synchronizes the settings file to all projects (except
tests.)

Change-Id: Iad7060523b6ee2cbbca97e0a6ffedb264b185222
Fix warnings 2012-06-01T19:30:40+00:00 Tor Norbye tnorbye@google.com 2012-06-01T19:30:27+00:00 764d9297c9631f239c8ebafc64edc77db80ce3c2 First, update our various project-specific Eclipse compiler settings configuration files to include the new Eclipse 4 flags. Second, turn off the "Unchecked conversion from non-annotated type to @NonNull" warnings; there are hundreds or thousands of these, and there isn't much we can do about them when they're coming from platform and library APIs. Third, make the lint projects warning-clean again by addressing various warnings Eclipse found (such as some unclosed resources and some null handling issues; yesterday's null annotation fixes only addressed errors, not warnings.) Change-Id: If75f7401a1cbeef1bf58b47ccaa9ad17bede7f91 
First, update our various project-specific Eclipse compiler settings
configuration files to include the new Eclipse 4 flags.

Second, turn off the "Unchecked conversion from non-annotated type to
@NonNull" warnings; there are hundreds or thousands of these, and
there isn't much we can do about them when they're coming from
platform and library APIs.

Third, make the lint projects warning-clean again by addressing
various warnings Eclipse found (such as some unclosed resources and
some null handling issues; yesterday's null annotation fixes only
addressed errors, not warnings.)

Change-Id: If75f7401a1cbeef1bf58b47ccaa9ad17bede7f91
Make some SDK project compile under Java 1.6 2012-02-02T23:38:35+00:00 Xavier Ducrohet xav@android.com 2012-02-02T23:04:59+00:00 f526dc3bb658b07c5a96d0372b17ffa2fbbe6079 Change-Id: I97189bda85530decff2ef8c4da3c43f186a6dba0 
Change-Id: I97189bda85530decff2ef8c4da3c43f186a6dba0