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

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

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

   In fact, IMHO we should revisit ALL these plugins having "artifact-like" 
(GAV) parameters and using resolver to resolve them, and
   * mark all these configurations as "usable for out-of-reactor plugins only" 
(or it is user who needs to hack in proper build order by whatever means he can)
   * come up with some proper solution in Maven to make sorting aware of ALL 
these
   
   Biggest problem is that "by chance" the ordering may be good, and seemingly 
everything works, but then user changes something completely unrelated (ie. 
adds a new module to build), that changes build order, and suddenly this 
breaks. In this situations is hard to figure out why breakage happened.




> 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