Add unsafe signatures for Java 8, review Java 7

[GoogleCodeExporter]

Currently Java 7 and Java 8 unsafe signatures are just copies of Java 6.

We should check especially Java 8 for new method signatures that use default 
charset, default locale, and default timezone. Java 7 is unlikely that new ones 
are introduced, but Java 8 has many new ones (because of introduction of 
closures).

Original issue reported on code.google.com by uwe.h.schindler on 9 Nov 2013 at 11:29

[GoogleCodeExporter]

This is a followup of issue #16.

Original comment by uwe.h.schindler on 9 Nov 2013 at 11:30

[GoogleCodeExporter]

We also need a way to validate those signatures in test cases. This is not easy 
to do, because you need the correct JDK at test runtime. We compile 
forbidden-apis with Java 5 only.

The idea is to have a special test, that loads the signatures matching the 
current JVM. Just to validate that they are correct.

jdk-deprecated does not need any test, because the signatures are autogenerated.

Original comment by uwe.h.schindler on 14 Sep 2014 at 5:22

[GoogleCodeExporter]

For now I committed a new offender in Java 7: Scanner#<init>(java.nio.file.Path)

Original comment by uwe.h.schindler on 14 Sep 2014 at 6:49

[GoogleCodeExporter]

I committed an Ant target to check the signatures for the current JVM: "ant 
check-bundled-signatures" (revision 312 and revision 313)

Original comment by uwe.h.schindler on 14 Sep 2014 at 10:01

[uschindler]

I close this issue because it looks like done. I opened another issue separately to review Java 7 and Java 8 again.