[ https://issues.apache.org/jira/browse/SUREFIRE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738441#comment-17738441 ]
ASF GitHub Bot commented on SUREFIRE-2179: ------------------------------------------ kwin commented on code in PR #667: URL: https://github.com/apache/maven-surefire/pull/667#discussion_r1246327954 ########## maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java: ########## @@ -281,6 +285,26 @@ public abstract class AbstractSurefireMojo extends AbstractMojo implements Suref @Parameter(property = "maven.test.additionalClasspath") private String[] additionalClasspathElements; + /** + * Additional Maven dependencies to be used in the test execution classpath. Review Comment: ```suggestion * Additional Maven dependencies to be added to the test classpath at runtime ``` > additionalClasspathElements should support Maven coordinates > ------------------------------------------------------------ > > Key: SUREFIRE-2179 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2179 > Project: Maven Surefire > Issue Type: Improvement > Components: classloading > Affects Versions: 3.1.2 > Reporter: Konrad Windszus > Assignee: Konrad Windszus > Priority: Major > > Currently the parameter {{additionalClasspathElements}} > (https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#additionalclasspathelements) > only supports file paths. That usually requires to add an additional step to > first download the necessary artifact to a temporary folder with another > Mojo. In addition {{additionalClasspathElements}} only support full paths to > JARs but no wildcards which makes configuration very verbose. > For these reasons there should be an additional parameter supporting Maven > coordinates which are then resolved automatically (even transitively) and > added to the test execution classpath. -- This message was sent by Atlassian Jira (v8.20.10#820010)