We could build on minimum jdk we support for testing pr's - which will
automatically cause build failures in case code uses newer api ?

Regards,
Mridul

On Fri, May 1, 2015 at 2:46 PM, Reynold Xin <r...@databricks.com> wrote:
> It's really hard to inspect API calls since none of us have the Java
> standard library in our brain. The only way we can enforce this is to have
> it in Jenkins, and Tom you are currently our mini-Jenkins server :)
>
> Joking aside, looks like we should support Java 6 in 1.4, and in the
> release notes include a message saying starting in 1.5 we will drop Java 6
> support.
>
>
>
>
> On Fri, May 1, 2015 at 2:00 PM, Thomas Graves <tgra...@yahoo-inc.com> wrote:
>
>> Hey folks,
>>
>> 2 more things that broke jdk6 got committed last night/today.  Please
>> watch the java api's being used until we choose to deprecate jdk6.
>>
>> Tom
>>
>>
>>
>>   On Thursday, April 30, 2015 2:04 PM, Reynold Xin <r...@databricks.com>
>> wrote:
>>
>>
>> This has been discussed a few times in the past, but now Oracle has ended
>> support for Java 6 for over a year, I wonder if we should just drop Java 6
>> support.
>>
>> There is one outstanding issue Tom has brought to my attention: PySpark on
>> YARN doesn't work well with Java 7/8, but we have an outstanding pull
>> request to fix that.
>>
>> https://issues.apache.org/jira/browse/SPARK-6869
>> https://issues.apache.org/jira/browse/SPARK-1920
>>
>>
>>
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e-mail: dev-h...@spark.apache.org

Reply via email to