1. I do not suspect, I'm sure of a difference 2. I do love exec but it is irrelevant for your test 3. tamas gave you all tooling to do the inspection 4. "Both exec plugin and *maven-dependency-plugin resolve to the same classpath*" <- I showed your it was not the case (with reasons for a part and bug for another) 5. "The bug reproduces with pure Maven APIs." <- yes but depending how you do use it you end with different results - it enables all cases, your demonstration is just not a proof currently
Side note: assuming you do proove maven should be gradle you will still hit the other issues, my advice is really to take the week end to think about it wider than your PoC and as an ecosystem thing. Gradle solution is not that great in practise except for trivial cases. For these last ones it saves to import the boms, that is the only advantage but you have way more cases it is an issue, this is why i'm not sure it is worth it at all. Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino founder (Java/.NET service - contact via linkedin) Le jeu. 6 nov. 2025 à 20:49, Vladimir Sitnikov <[email protected]> a écrit : > >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 >
