GitHub user Leemoonsoo opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/720

    Bringing compiledScope for backward compatibility

    ### What is this PR for?
    compiledScope was not exposed API for users.
    However, some users were using compiledScope in their notebook and 
[ZEPPELIN-551](http://issues.apache.org/jira/browse/ZEPPELIN-551) break this 
notebook work by removing compiledScope.
    
    https://gist.github.com/granturing/a09aed4a302a7367be92 is an example 
notebook that uses compiledScope.
    
    This PR bringing compiledScope back for backward compatibility.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    * [x] - Bringing compiledScope back for backward compatibility
    
    ### Is there a relevant Jira issue?
    compiledScope was removed by 
http://issues.apache.org/jira/browse/ZEPPELIN-551 
    
    
    ### How should this be tested?
    
    Test https://gist.github.com/granturing/a09aed4a302a7367be92
    
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no

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

    $ git pull https://github.com/Leemoonsoo/incubator-zeppelin 
bringing_compiledScope

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

    https://github.com/apache/incubator-zeppelin/pull/720.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 #720
    
----
commit 0b6e5a8d80179e4bb60b238fb4136e94f1b283ab
Author: Lee moon soo <m...@apache.org>
Date:   2016-02-16T19:33:10Z

    Bringing compiledScope for backward compatibility

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to