[MINVOKER-285] Consider of using groovy-all once again

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0
• Assignee: Sylwester Lachiewicz
• Reporter: Slawomir Jaranowski
• Created: 16/Sep/21 14:17
• Updated: 01/Dec/21 00:34
• Resolved: 01/Dec/21 00:34

Description

Current on classpath we have:

+- org.codehaus.groovy:groovy-all:pom:3.0.8:runtime
|  +- org.codehaus.groovy:groovy:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-ant:jar:3.0.8:runtime
|  |  +- org.apache.ant:ant:jar:1.10.9:runtime
|  |  +- org.apache.ant:ant-junit:jar:1.10.9:runtime
|  |  |  \- com.sun:tools:jar:1.8.0:system
|  |  +- org.apache.ant:ant-launcher:jar:1.10.9:runtime
|  |  \- org.apache.ant:ant-antlr:jar:1.10.9:runtime
|  +- org.codehaus.groovy:groovy-astbuilder:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-cli-picocli:jar:3.0.8:runtime
|  |  \- info.picocli:picocli:jar:4.5.2:runtime
|  +- org.codehaus.groovy:groovy-console:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-datetime:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-docgenerator:jar:3.0.8:runtime
|  |  \- com.thoughtworks.qdox:qdox:jar:1.12.1:runtime
|  +- org.codehaus.groovy:groovy-groovydoc:jar:3.0.8:runtime
|  |  \- com.github.javaparser:javaparser-core:jar:3.18.0:runtime
|  +- org.codehaus.groovy:groovy-jmx:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-json:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-jsr223:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-macro:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-nio:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-servlet:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-sql:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-swing:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-templates:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-test:jar:3.0.8:runtime
|  +- org.codehaus.groovy:groovy-test-junit5:jar:3.0.8:runtime
|  |  +- org.junit.jupiter:junit-jupiter-api:jar:5.7.0:runtime
|  |  |  \- org.opentest4j:opentest4j:jar:1.2.0:runtime
|  |  +- org.junit.platform:junit-platform-launcher:jar:1.7.0:runtime
|  |  |  \- org.junit.platform:junit-platform-engine:jar:1.7.0:runtime
|  |  |     \- org.junit.platform:junit-platform-commons:jar:1.7.0:runtime
|  |  \- org.junit.jupiter:junit-jupiter-engine:jar:5.7.0:runtime
|  +- org.codehaus.groovy:groovy-testng:jar:3.0.8:runtime
|  |  \- org.testng:testng:jar:7.4.0:runtime
|  |     +- com.beust:jcommander:jar:1.78:runtime
|  |     \- org.webjars:jquery:jar:3.5.1:runtime
|  \- org.codehaus.groovy:groovy-xml:jar:3.0.8:runtime

Problems

The one of problem which I see is that we have transitive dependency to:

• junit-jupiter-api
• testng

In project (currently) we use junit4 - it is declared on direct dependency,
but surefire use testng

[INFO] Running TestSuite
Configuring TestNG with: TestNG60Configurator

So junit tests are executed by testng framework ... I don't sure if it is expected behavior

Options

• exclude next dependency from groovy-all like groovy-test-junit5, groovy-test, groovy-testng or exclude conflicted artifacts like testng ....

• or back to list only needed groovy modules ....

Issue Links

• blocks: MINVOKER-284 Upgrade JUnit to version 5, drop maven-compat
• is related to: MINVOKER-138 Add groovy-all dependency instead of groovy by default
• is related to: MINVOKER-274 Use Groovy 3.x to prevent Java9+ warnings about Groovy 2.x using illegal reflection
• relates to: SUREFIRE-1963 Detecting multiple test-frameworks
• links to: GitHub Pull Request #77