Re: [Jflex-devel] Minimum build JDK: 6->7 ?

[Steve R. <sa...@gm...>]

Hi Gerwin,

> On Mar 8, 2017, at 10:13 PM, Gerwin Klein <ge...@do...> wrote:
> 
> Sorry, have overlooked this somehow. Yes, no problem from my side with switching the minimum supported build to 1.7.

Cool, thanks.

> It’d be nice to make the test suite aware of JDK version at the points where it is sensitive to that. If I remember correctly the failure was just a different output order of a Hashtable or similar.

What sort of awareness are you thinking of?  Allowing only a single version of the JDK?  Or switching between expected output depending on JDK version?  Or…?

> Do you want to push the change directly?

Sure, I’ll do that some time this week.

Steve

>> On 14.02.2017, at 01:55, Steve Rowe <sa...@gm...> wrote:
>> 
>> Hi Gerwin,
>> 
>> I’m working on adding Unicode 9.0 support to JFlex, and I noticed that my Maven version (3.3.9) no longer supports Java 6, which is documented as JFlex's minimum supported build version.
>> 
>> When the Travis build for the Add_Unicode-9.0 branch failed <https://travis-ci.org/jflex-de/jflex/builds/201132195>, I noticed that it’s configured to use Java 8.  The docs say that Java 6 is not supported - from <https://docs.travis-ci.com/user/ci-environment/>:
>> 
>>> Sun/Oracle JDK 6 is not provided because it reached End of Life in fall 2012.
>> 
>> On the Add_Unicode-9.0 branch I reconfigured Travis to use Java 7, which stopped the ccl-pre testsuite test from failing (the jflex output differed under Java8). 
>> 
>> I think we should switch the minimum supported build JDK for JFlex from 1.6 to 1.7.
>> 
>> Steve