You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2021/09/16 14:18:00 UTC
[jira] [Created] (MINVOKER-285) Consider of using groovy-all once
again
Slawomir Jaranowski created MINVOKER-285:
--------------------------------------------
Summary: Consider of using groovy-all once again
Key: MINVOKER-285
URL: https://issues.apache.org/jira/browse/MINVOKER-285
Project: Maven Invoker Plugin
Issue Type: Improvement
Reporter: Slawomir Jaranowski
Current on classpath we have:
{code:java}
+- 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
{code}
h2. 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}}
{code:java}
[INFO] Running TestSuite
Configuring TestNG with: TestNG60Configurator
{code}
So {{junit}} tests are executed by {{testng}} framework ... I don't sure if it is expected behavior
h2. 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 ....
--
This message was sent by Atlassian Jira
(v8.3.4#803005)