Github user justsomeone1001 commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-181674445
  
    @bzz Thank you for your attention and efforts to move this forward!
    
    I'm happy to do all the required work (but I'm really just stuck on CI).  
    
    I think you have hit the issues.   Let me give the status of a few:
    
    1. (Other modules.)  There are small changes to spark/ that are necessary.  
There are also changes to the pom.xml's in spark, spark-dependencies, and the 
main one.  I don't *think* they're necessary, but they do resolve some 
persistent issues people have had building with different variants of spark. 
    
    2.  (Rebase.)  This:  https://github.com/elbamos/Zeppelin-With-R  Is 
up-to-date with 0.5.6.  I will bring this branch up to date with current 
master. 
    
    3.  (Docs.)  Docs are included with the URL above and will be in the 
rebased PR. 
    
    4.  (CI) Thank you!
    
    5.  (Licenses.)  The code under r/ is ASF, but some files are derived from 
BSD-licensed rscala code.  Also, some files under r/ are not code.  They're 
generated during the R-package build process, so they don't have licenses at 
the top.  I think this is some of what Jongyoul was on about.  I'm happy to 
take care of this however, but just need to know how it should look. 
    
    6.  (pom.xml formatting.)  Can you clarify what's required?  
    
    7.  (Source formatting.)  Will-do.
    
    Also - we should probably change the build so that R is either a module, or 
builds only if R is present.  Something also needs to be done so it gets 
included in the binary build.  
    
    I will work on this over the next few days, but I'm trying to respect the 
moratorium. 
    
    



---
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