Yes, early accesses are to solicit feedback, and we've been doing just that for
the past year or more. But it's also true that we have to stop accepting
feedback and ship at some point, or otherwise we can never ship anything. And
unfortunately, that time is now.
I don't know if you've seen this or not, but we just released the release
candidate of the RI, and the spec has already or is shortly going to go for the
final vote in JCP. So the kind of fixes we can make at this point for 2.0 is
fairly limited, and this is clearly not one of them, since this is very much an
intrusive change — any change that makes a difference in the generate
signature is an intrusive change.
I re-opened issue for 2.0.1 as an RFE to see if there's anything we can do. But
the thing is, since the spec decides the signature that we generate, we can't
really just "fix" this in the RI. There's a backward compatibility aspect, too
— if we change the generated signature, it causes a trouble to a lot of people.
But perhaps you (or someone) might be able to write a plugin to fix this, or we
might be able to have a vendor-extension customization.
The reason I mentioned auto-boxing is that you can write:
boolean b = foo.isBar();
even if isBar returns Boolean.