[3.0] [flink-cdc-dist] Collect all distro resources into a TAR#2636
[3.0] [flink-cdc-dist] Collect all distro resources into a TAR#2636PatrickRen merged 7 commits intoapache:masterfrom
Conversation
88cbd6c to
6d2bc12
Compare
32ce5a6 to
59ff733
Compare
59ff733 to
78bcda5
Compare
78bcda5 to
9fdb79d
Compare
PatrickRen
left a comment
There was a problem hiding this comment.
@GOODBOY008 Thanks for the PR! I left some comments.
| <dependencySets> | ||
| <dependencySet> | ||
| <unpack>false</unpack> | ||
| <scope>runtime</scope> |
There was a problem hiding this comment.
I found some suspicious JARs in the final tarball:
- Awaitility: This should be a test dependency, and should not be a part of the distribution. We need to change its scope to
testin pom. - Hamcrest: This is defined as test scope in out project, but brought into the project as
compileby Awaitility. I guess it will disappear once we change Awaitility to test scope. - flink-cdc-dist: This is a JAR without any class file inside. We can just skip it when assembling.
- commons-cli: What about packaging it directly into
flink-cdc-cli?
Things missing:
- Log4j JAR and config file: Users cannot have logging locally without them
There was a problem hiding this comment.
About log4j I made a second thought, that maybe it's better to use log4j JARs under FLINK_HOME directly. We just need to provide a log4j configuration file for printing Flink CDC CLI and composer logs to a local file. Sorry for that!
9fdb79d to
e9534dd
Compare
- flink-cdc-dist should depends on all Flink CDC modules to enforce the building order - Package a uber JAR with all Flink CDC classes and dependencies - Remove the profile to make packaging flink-cdc-dist as the default behavior
- Keep a directory under target for easier validation - Add logic for copying flink-cdc-dist uber JAR to lib
|
I pushed 4 commits to the PR just now:
@GOODBOY008 Could you take a look at the PR? I checked the packaged tarball and it should work as expected now. |
|
@PatrickRen I tested on my local, works as we want. Thank you for complete my rest work and address issue. 👍 |
leonardBang
left a comment
There was a problem hiding this comment.
Thanks @GOODBOY008 and @PatrickRen for the great work, I went through the files, LGTM
…e#2636) This closes apache#2621 apache#2622 Co-authored-by: Qingsheng Ren <renqschn@gmail.com>
…e#2636) This closes apache#2621 apache#2622 Co-authored-by: Qingsheng Ren <renqschn@gmail.com>
Close #2621 #2622