Yes, Because the release binary packages don't contain connectors v2, So we don't need to pay attention to relevant licenses.
Jared <[email protected]> 于2022年7月13日周三 03:49写道： > It's a good idea to separate SeaTunnel core and connectors when > release. > > > But There is a question: > Don't we need to sort out the licenses of third-party jars when > develop new connector ? > > > Jared > [email protected] > > > > > > > > > ------------------ 原始邮件 ------------------ > 发件人: > "dev" > < > [email protected]>; > 发送时间: 2022年7月12日(星期二) 下午3:02 > 收件人: "dev"<[email protected]>; > > 主题: [proposal] ConnectorV2 no longer provides binary packages > > > > Hi, everyone. > > Because seatunnel connectors are developed independently, each connector > needs to rely on a large number of third-party jar packages, and > contributors need to spend a lot of energy to sort out the licenses of > these third-party jars, which brings great difficulties to the development > of connector. Therefore, I propose that the binary package of the new > connector will not be released at the same time when seatunnel is released, > which can improve the time of connector development. > > > We use Maven profiles to control the build process. By default, all modules > will be built. When we check-dependency in CI or release project, we can > set e2e, examples, connectors-v2, connectors-v2-dist,dependency-shade not > to build through "-P release" > > > We recommend that users compile their own seatunnel connector. > > -- > > Best Regards > > ------------ > > EricJoy2048 > [email protected] -- Best Regards ------------ EricJoy2048 [email protected]
