Le 2023-12-19 à 11 h 36, Guillaume Nodet a écrit :
Ideally, you'd only focus on org.apache.maven.api.* and forget about everything else. That's the Maven 4 API and all other things are not part of that API (including MavenProject). The class path resolution should be done using the following code:(…snip…) for (Dependency dependency : result.getDependencies().keySet()) { DependencyProperties properties = dependency.getDependencyProperties(); ... }
Thanks, I will adapt the code proposal. But above example gets only the list of dependencies. Is there is central place in Maven 4 API for doing the next step, which is to build the class-path, etc. from this set, or is it expected that each plugin would do this work themselves? In the latter case, I would like to replace this assumption by an API doing this work for plugins. Plugins would not be forced to use that API, but encouraged.
Martin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
