Hi Thomas,
Thomas Neidhart wrote:
> On 11/13/2013 11:04 AM, Jörg Schaible wrote:
>> Hi Thomas,
>>
>> Thomas Neidhart wrote:
>>
>>> Hi Joerg,
>>>
>>> the failure for JDK 1.8 is clear: this version updated the Map interface
>>> with a new method boolean remove(Object, Object) which clashes with the
>>> ones in MultiValueMap and MultiMap. We should change the return type to
>>> be compatible.
>>
>> This means unfortunately that I will vote with -1. If this new method
>> stays in J8, we would have to make an incompatible change ourselves for
>> J8- compatibility :-(
>>
>>> For IBM JDK 6: I did already ignore several tests (due to problems with
>>> the TreeMap implementation there) if run with this JVM but obviously
>>> something has changed since then, need to check.
>>
>> I can tell you this evening (in ~6 hours), which version I used exactly.
>> However, IIRC the number of executed tests were for me always the same.
>> Maybe the check for IBM JDK 1.6 failed?
>>
>>>
>>> For IBM JDK 5: It only fails to compile the tests, but I could not yet
>>> figure out why.
>>
>> Same to me. BTW: I forget in my list below to mention that I can run with
>> IBM JDK 1.5 all tests successfully if I use the compiled classes of Sun
>> JDK 1.5.
>
> The compiler does not like constructs like this:
>
> for (@SuppressWarnings("unused") final String element : array) {
> iterator.next();
> }
>
> Removing the @SuppressWarnings solves it.
> I guess this creates an internal compiler error, that's why we don't see
> any message / error.
Gosh. This is so stupid. Alas, trunk compiles now. All tests are fine.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
