I have recorded some things that can be communicated after the merge: 1. protostuff dependencices: currently only used by engine, but managed in root pom,xm. 2. transform api: We need to unify the transform, but the current one is very simple, and there may be many problems. 3. seatunnel core pom.xml & assembly-bin.xml & transforms pom.xml: The release and all profiles are the same. 4. seatunnel-engine-e2e: e2e has been unified based on connector-v2 api. 5. [SeatunnelErrorEnum.java]( https://github.com/apache/incubator-seatunnel/pull/2928/files#diff-1f1f1266f69dafd94bc60c860dcf0fdaa900881b5e24aa9bf73b45c277bbd448 )
Best, Zongwen Li CalvinKirs <[email protected]> 于2022年9月28日周三 21:18写道： > > > Well done, thanks Jia, I will take a look > > > Best wishes！ > Calvin Kirs > > > On 09/28/2022 20:51，Jia Fan<[email protected]> wrote： > Hi contributers of SeaTunnel. > > After engine already finished main feature of MVP version. So we want to > merge st-engine branch to dev. > Lots of code have conflict. So Try my best when I merge code, but I > probably have some mistake be made. So can you help me to check the code > again? It’s will be very helpful. > The PR link: https://github.com/apache/incubator-seatunnel/pull/2928 < > https://github.com/apache/incubator-seatunnel/pull/2928> > > I follow these guidelines when merging code： > seatunnel-connectors-v2 based on dev branch > seatunnel-engine based on st-engine branch > seatunnel-server and seatunel-ui based on dev branch > seatunnel-core based on dev branch > > Thanks! > > ________________________ > > Jia Fan > > > >
