[ 
https://issues.apache.org/jira/browse/SUREFIRE-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738425#comment-17738425
 ] 

ASF GitHub Bot commented on SUREFIRE-2179:
------------------------------------------

cstamas commented on PR #667:
URL: https://github.com/apache/maven-surefire/pull/667#issuecomment-1612598248

   For all non POM/dependency and POM/plugins/plugin/dependency elements, 
especially for plugin config like this one (or like compiler anno processor is, 
etc) we MUST BE CLEAR that it works ONLY for _external dependencies_. These 
elements do NOT participate in project topological sorting, hence, becomes 
impossible to use some reactor project for these (without hacks). Moreover, if 
using reactor artifacts, this is one of the reasons why users are forced to to 
`mvn install` as 1st pass, and from 2nd pass onward "it will work", but again, 
what is being used "lags" one build cycle (as installed thing is being used, 
not the currently built one). 
   
   See for example here https://issues.apache.org/jira/browse/MNG-6877




> 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)

Reply via email to