Hi, If you run maven dependency:tree, which version of the maven-dependency-plugin do you see? (Look for something like: [INFO] --- maven-dependency-plugin:3.1.2:tree (default-cli) @ your-module )
And if it is something other than 3.1.2: * Why aren't you using the latest version? * Why don't you specify the plugins you are using in the pluginManagement section of your company pom? Ensuring the build environment is consistent is critical. Use the pluginManagement section in the parent POM to declare explicit plugin versions. This will nail down the plugin environment, removing potential future conflicts. It’s still good practice to regularly check for and update to the latest versions. Hth, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Thu, Jul 9, 2020 at 12:37 AM Anton Vodonosov <[email protected]> wrote: > Hi, thank you for the responses. > > Currently I was trying on a multi-module project, and > > mvn dependency:tree > > fails complaining about the impossibility to find artifact for one of the > reactor modules, but > > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:tree > > works. I've tried to debut a little but was unable to understand the > reason. > > So you say it should work for the whole project, but can fail if we > specify a subset of modules? > > In the past me and my colleagues were always building the project when > studying the dependency tree. > I don't remember when it failed, for the whole project or maybe we > encountered failures > when specifying specific modules using the -pl option. > > I will follow up if I have more info. > > Best regards, > - Anton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
