[hotfix][e2e] refactor jupiter,add junit-jupiter-api

[liugddx]

Purpose of this pull request

refactor jupiter,add junit-jupiter-api

Check list

• Code changed are covered with tests, or it does not need tests for reason:
• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

[TyrantLucifer]

Can you explain why you want to add this dependency?

[CalvinKirs]

the e2e module used junit 4.

[liugddx]

Occasionally switching branches leads to inconsistent versions of api dependencies

[CalvinKirs]

I think we have declared these dependencies, junit-jupiter-params inculde juitper-api
if you checked. e2e We use junit4 and 5 for Testcontainers reasons

[liugddx]

I think we have declared these dependencies, junit-jupiter-params inculde juitper-api if you checked. e2e We use junit4 and 5 for Testcontainers reasons

but the e2e dependence jupiter.if the junit-jupiter-api has a different versions.the error will happen.

[ashulin]

In which dependency will junit-jupiter-api-5.8.2 be referenced?

[liugddx]

In which dependency will junit-jupiter-api-5.8.2 be referenced?

i dependence spring-boot-dependencies,and the junit-jupiter.versionis 5.8.2.

[ashulin]

This PR contains the reason: #2672 . I ran CI again.

[CalvinKirs]

hi, we better revert https://github.com/apache/incubator-seatunnel/blob/34ccfd7a2cd93d8dc0d3f6bb1e1afebcc9761a9e/pom.xml#L360
This modification changes so many dependencies that I suspect there are still a lot of potential issues that haven't been discovered, but as long as we revert it, this issue and other issues can be resolved.

[CalvinKirs]

revert this change

[zhuangchong]

My suggestion is to introduce junit-bom for dependency management and remove junit-jupiter-engine and junit-jupiter-params with the following changes:

add:

  <dependency>
      <groupId>org.junit</groupId>
      <artifactId>junit-bom</artifactId>
      <version>${junit.version}</version>
      <type>pom</type>
      <scope>import</scope>
  </dependency>

remote:

<dependency>
      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter-engine</artifactId>
      <version>${junit.version}</version>
      <scope>test</scope>
  </dependency>

  <dependency>
      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter-params</artifactId>
      <version>${junit.version}</version>
      <scope>test</scope>
  </dependency>

update:

<dependencies>
...
 <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter-engine</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter-params</artifactId>
            <scope>test</scope>
        </dependency>

    </dependencies>

[zhuangchong]

UserControllerTest executes an error after the scheduler function is added to the web module, because the web module needs to connect to the dolphinscheduler server, I will deal with this problem.