| commit | 19c86f20500a7fd9b4ce5ca42caf42337863f2a8 | [log] [tgz] |
|---|---|---|
| author | Prashant Kumar <65131575+pkumar-singh@users.noreply.github.com> | Fri Apr 09 10:30:20 2021 -0700 |
| committer | GitHub <noreply@github.com> | Fri Apr 09 10:30:20 2021 -0700 |
| tree | f8703ad1fc8771b7800a4782832744f3f34327ca | |
| parent | acbc20dacf3d13c91a872c24e45d0c4d69bb9733 [diff] |
ISSUE #2640: BP-43 create shaded jar for bookkeeper-server and distrib… …utedlog-core Descriptions of the changes in this PR: ### Motivation **Gradle migration** With maven shaded Jar was created for bookkeeper-sever as well as distributedlog-core. Though shaded jar was not being used by anybody. There has been some difference in layout of shaded jar produced by maven and gradles. Maven produced shaded jar just shades bookkeeper classes and leaves transitive dependency unshaded and as part of dependency in POM file. This behavior is not supported in gradle shadow plugin. Therefore gradle produced shaded jar shades not only bookkeer-server but also its transitive and direct dependencies and leaving nothing in pom file as dependency. ### Changes Create gradle build for shading bookkeeper-sever and distributedlog-core Master Issue: #2640 Reviewers: Henry Saputra <hsaputra@apache.org>, Matteo Merli <mmerli@apache.org> This closes #2678 from pkumar-singh/merge_internal_gradle_6, closes #2640 and squashes the following commits: 3f9cb7e9f [Matteo Merli] Merge branch 'master' into merge_internal_gradle_6 acbc20dac [Prashant Kumar] ISSUE #2640: BP-43 Integrate checkstyle with gradle f46021c4c [Prashant] ISSUE-2640: BP-43 create shaded jar for bookkeeper-server and distributedlog-core 59786c97f [Prashant Kumar] ISSUE #2640: BP-43: Exclude smoke tests for now can be enabled when we move to gradle.
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.