GitHub user vanzin reopened a pull request:

    https://github.com/apache/spark/pull/11941

    [SPARK-14134] [core] [test-maven] Change the package name used for shading 
classes.

    The current package name uses a dash, which is a little weird but seemed
    to work. That is, until a new test tried to mock a class that references
    one of those shaded types, and then things started failing.
    
    Most changes are just noise to fix the logging configs.
    
    For reference, SPARK-8815 also raised this issue, although at the time it
    did not cause any issues in Spark, so it was not addressed.

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

    $ git pull https://github.com/vanzin/spark SPARK-14134

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

    https://github.com/apache/spark/pull/11941.patch

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

    This closes #11941
    
----
commit 9ecbafbd6c52a998d729889b520a29ba476b27ed
Author: Marcelo Vanzin <[email protected]>
Date:   2016-03-24T18:15:26Z

    [SPARK-14134] [core] Change the package name used for shading classes.
    
    The current package name uses a dash, which is a little weird but seemed
    to work. That is, until a new test tried to mock a class that references
    one of those shaded types, and then things started failing.
    
    Most changes are just noise to fix the logging configs.

commit 0f863b4f6d6c135471a54ec0bbce4a2e7842816c
Author: Marcelo Vanzin <[email protected]>
Date:   2016-03-28T17:44:06Z

    Merge branch 'master' into SPARK-14134

commit 81af47b4cc7e596c66a169f7724a3ef7e7bf9d3b
Author: Marcelo Vanzin <[email protected]>
Date:   2016-03-28T17:46:06Z

    Fix a few more references to the old package.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. 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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to