You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2014/07/07 04:00:34 UTC

[jira] [Updated] (SAMZA-202) Support Java 8

     [ https://issues.apache.org/jira/browse/SAMZA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan updated SAMZA-202:
------------------------------

    Attachment: SAMZA-202-draft.patch

Started on this, but not done yet.
* Switched to Gradle 2, which had a [build error that looks spurious and was based on an extra parameter|http://forums.gradle.org/gradle/topics/publishing_task_breaks_from_gradle_1_6_to_2_0_with_task_with_name_not_found?utm_source=notification&utm_medium=email&utm_campaign=new_reply&utm_content=topic_link]
* The Gradle publish task no longer publishes the md5 or sha1 files; this should probably be handled in another JIRA as it will likely require assistance from the Gradle guys.
* The license check plugin was using a removed Gradle command.  Upgraded to 0.9.  This version is better at catching unlicensed files (the css and js files), but still has no way to whitelist individual files.  Since we're going to RAT, I've just turned on the treat-these-as-warnings flag, which gives us the same behavior as before.
* Running into a bigger issue with Jetty and Samza YARN.  We bring in Jetty 8 for our web servers but YARN uses Jetty 6 (and is pretty stuck on that version).  Java 8 has a problem with the jars between the two as they're signed differently and fails (at least) testAppMasterDashboardShouldStart (with "java.lang.SecurityException: class "javax.servlet.HttpConstraintElement"'s signer information does not match signer information of other classes in the same package"  At least this is my guess based on initial stack overflowing; this appears to be a common error.

Need to poke a bit more to confirm it's Jetty that's the culprit, but if so, we'll have a tough time sorting these jars.  It will be difficult to sort out the servlets we run in our AM from the AM/YARN logic itself...

> Support Java 8
> --------------
>
>                 Key: SAMZA-202
>                 URL: https://issues.apache.org/jira/browse/SAMZA-202
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Garry Turkington
>            Assignee: David Chen
>            Priority: Minor
>         Attachments: SAMZA-202-draft.patch
>
>
> We were late to the party with Java 7 support so opening this to get a head-start on Java 8 support.



--
This message was sent by Atlassian JIRA
(v6.2#6252)