GitHub user minahlee opened a pull request:

    https://github.com/apache/zeppelin/pull/1427

    [ZEPPELIN-1435] Move zeppelin-server-*.jar under lib in distribution binary 
package

    ### What is this PR for?
    Move zeppelin-server-*.jar package under `lib` directory like other 
zeppelin modules such as `zeppelin-engine`, `zeppelin-interpreter`
    
    ### What type of PR is it?
    Refactoring
    
    ### What is the Jira issue?
    [ZEPPELIN-1435](https://issues.apache.org/jira/browse/ZEPPELIN-1435)
    
    ### How should this be tested?
    Build with:
    ```
    mvn clean package -DskipTests -Pbuild-distr -pl 
'!alluxio,!angular,!cassandra,!elasticsearch,!file,!flink,!hbase,!ignite,!jdbc,!kylin,!lens,!livy,!postgresql,!python,!shell,!bigquery'
    ```
    
    and check if `zeppelin-server-0.7.0-SNAPSHOT.jar` file is placed under 
`zeppelin-distribution/target/zeppelin-0.7.0-SNAPSHOT/zeppelin-0.7.0-SNAPSHOT/lib`
 not 
`zeppelin-distribution/target/zeppelin-0.7.0-SNAPSHOT/zeppelin-0.7.0-SNAPSHOT`
    
    ### 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/minahlee/zeppelin ZEPPELIN-1435

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

    https://github.com/apache/zeppelin/pull/1427.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 #1427
    
----
commit 03a018f7dbb6f43ab72a71735e0e1203e716f73a
Author: Mina Lee <[email protected]>
Date:   2016-09-13T13:42:03Z

    Move zeppelin-server-*.jar under lib in distribution binary 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.
---

Reply via email to