>Please looking exec plugin comment. There are two comments:
https://lists.apache.org/thread/khs6l9zl2wfd99g8t4p8mgd7o3wxqgnd >side note: exec resolution can differ from dependency plugin (and other > plugins) and https://lists.apache.org/thread/19bg02q09njgbzymkq8w6463b5c64jrx >add v2 as depMgt, it does resolve deps in v2 as written in my previous mail >but exec print 1.0.0 in your main so likely a bug in exec which doesn't use >the strict resolution of resolver In both messages you suspect a bug in the exec plugin. Exec plugin uses org.apache.maven.project.MavenProject#getRuntimeArtifacts() https://github.com/mojohaus/exec-maven-plugin/blob/cdaf2670882694beaa597e3ecacaeb5493ee31fc/src/main/java/org/codehaus/mojo/exec/AbstractExecMojo.java#L200C30-L200C59 It is a single Maven public API call, and I do not see a room for a bug there. I see you don't like exec plugin. What approach would you recommend to verify resolution from the end user's point of view? Please pay attention that reproducer includes both exec plugin and *apache/maven-dependency-plugin* which is *released by Maven PMC*. Both exec plugin and *maven-dependency-plugin resolve to the same classpath*, so if there's a bug, the bug is the same between the plugins. It is unfair to say "the example is not relevant because you use a third-party plugin". The bug reproduces with pure Maven APIs. Vladimir
