spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From srowen <>
Subject [GitHub] incubator-spark pull request: SPARK-1084 (part 1). Fix most build ...
Date Sun, 23 Feb 2014 23:29:53 GMT
GitHub user srowen opened a pull request:

    SPARK-1084 (part 1). Fix most build warnings.

    This is a redo of
    This contains all the same changes, minus dependency changes. It also rebases and squashes
some commits that could be combined.
    After this is in I'll propose part 2, which concerns dependencies.

You can merge this pull request into a Git repository by running:

    $ git pull SPARK-1084.1

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #637
commit 2e52f136474abf911472af2bb639d704605cd171
Author: Sean Owen <>
Date:   2014-02-11T14:37:03Z

    Replace deprecated Ant <tasks> with <target>

commit a82b841df207128aec23ae9eb3a297e41d1bcc49
Author: Sean Owen <>
Date:   2014-02-11T14:38:23Z

    Remove dead scaladoc links

commit 3b7b2ad9c9a2536da51a1b6af7ebf2aff77fef32
Author: Sean Owen <>
Date:   2014-02-11T14:39:48Z

    Fix scaladoc invocation warning, and enable javac warnings properly, with plugin config

commit b5ccbc9c6360437afabcfc14e81321e5b7b38e4c
Author: Sean Owen <>
Date:   2014-02-12T13:45:04Z

    Fix one new style error introduced in scaladoc warning commit

commit 79f1c7acdb9634128d417d704a234058d2993bea
Author: Sean Owen <>
Date:   2014-02-23T21:27:02Z

    Fix two misc javadoc problems

commit ee1c1150d482243c190c71931852f2797ec79120
Author: Sean Owen <>
Date:   2014-02-23T23:27:21Z

    Suppress warnings about legitimate unchecked array creations, or change code to avoid


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post your response.
If your project does not have this feature enabled and wishes so, or if the
feature is enabled but not working, please contact infrastructure at or file a JIRA ticket with INFRA.

View raw message