HIVE-29043: Ban the Jupiter dependency from hive-unit to prevent unit tests from being skipped

[abstractdog]

What changes were proposed in this pull request?

Ban jupiter dependency.

Why are the changes needed?

To prevent skipping hive-unit unit tests silently again.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Tested with adding the problematic dependency, and instead of silently skipping unit test, it failed.

mvn install -Pitests -Dtest=TestHttpServices -pl ./itests/hive-unit -nsu

...

[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
Found Banned Dependency: org.junit.jupiter:junit-jupiter:jar:5.11.2
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  11.237 s
[INFO] Finished at: 2025-06-24T14:56:04+02:00
[INFO] ------------------------------------------------------------------------
[INFO] 5 goals, 5 executed
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce (ban-jupiter) on project hive-it-unit: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]
[ERROR]

[zabetak]

I like the idea but based on the test failures it seems that we already have jupiter dependencies in the project so we have to revisit those.

Other than that left some minor suggestions for potential improvements.

[zabetak]

This comment would be more helpful if it was part of the failure. How about putting it in <message>...</message>

[zabetak]

Same comment regarding the message.

[zabetak]

I think the default is true so possible we could skip this.

[zabetak]

Why do we want to put the rule in a separate execution? We could merge enforce-banned-dependencies and ban-jupiter and it would lead to less boilerplate code.

[abstractdog]

I like the idea but based on the test failures it seems that we already have jupiter dependencies in the project so we have to revisit those.

Other than that left some minor suggestions for potential improvements.

thanks for the comments, finally, even if I wanted to ban the dependency globally so bad, I had to face that we do use the jupiter api extensively in some modules, so I ended banning it from itests/hive-unit, where it caused the problem all the time

there how I ended up with: 8e57d3b

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud