ailiujiarui commented on PR #16542: URL: https://github.com/apache/dolphinscheduler/pull/16542#issuecomment-2443770782
> > > Please don't add `.jar` in the source code, the `.jar` file will be excluded in src, these means the e2e will not be executed after release.请不要在源码中添加 `.jar`，`.jar` 文件将被排除在 src 中，这意味着 e2e 发布后不会执行。 > > > > > > +1. I suggest adding the source code of the test jar to e2e module as a submodule, and compiling the corresponding jar through `mvn package` for e2e to test+1.我建议将测试 jar 的源码作为子模块添加到 e2e 模块中，并通过 `mvn 包`编译相应的 jar 供 e2e 测试 > > cc: 抄送：@ailiujiarui @SbloodyS @ruanwenjun > > Agreed. 同意。 I first tried placing the three classes fat, normal1, and normal2 in the common package under e2e-case, then compiled and packaged them into JAR files through code to provide for other workflows. However, the problem arose because the worker uses Java 8, while e2etest uses Java 11. The JAR packaged under the e2e directory couldn't be executed by the worker, throwing an error due to a higher version. I then tried moving common to the resources package under e2e-case and created a shell workflow to compile these three classes using the worker and output them to /tmp. The code then packages them into a JAR, but the current issue is that it keeps reporting that it can't find [Fat.class ](https://fat.class/)under /tmp, resulting in an empty JAR. I don't know what the reason is. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
