Can't quite make sense of all this; given that you got no replies, maybe no one else understood either. Could you explain a bit better?
-----Original Message----- From: yukai zhao <yukz...@163.com> Sent: Monday, October 30, 2023 9:10 PM To: users@maven.apache.org Subject: Version Management in 'mvn dependency:tree' CAUTION: This email originated from outside our organisation - yukz...@163.com Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is safe. Hello, Recently, I attempted to use 'mvn dependency:tree' to retrieve the project's dependency tree. However, in the output, I noticed that for the same dependency with different scopes, its version doesn't appear to be consistent. The specific scenario is as follows: (org.checkerframework:checker-qual:jar:3.5.0:compile - scope updated from runtime; omitted for duplicate) org.checkerframework:checker-qual:jar:3.12.0:compile I made sure that these two pieces of information are present in the dependency tree of the same JAR. However, in the compilation information, I found that the first entry was hidden, and only the second entry was displayed. I'm curious about what happened here. In the actual compilation process, were both versions utilized, or was only the first version used? Additionally, I attempted to remove the existing dependency package of version 3.5.0 and recompile the project. Surprisingly, even after removing the 3.5.0 version dependency package, Maven still downloads and utilizes it. Does this indicate that the project is still using the 3.5.0 version of the dependency package? Of course, I need to add a clarification: the 3.5.0 version of the dependency package is an indirect dependency of the project, while version 3.12.0 is a direct dependency. Best regards, Yukai zhao This message is for information purposes only. It is not a recommendation, advice, offer or solicitation to buy or sell a product or service, nor an official confirmation of any transaction. It is directed at persons who are professionals and is intended for the recipient(s) only. It is not directed at retail customers. This message is subject to the terms at: https://www.cib.barclays/disclosures/web-and-email-disclaimer.html. For important disclosures, please see: https://www.cib.barclays/disclosures/sales-and-trading-disclaimer.html regarding marketing commentary from Barclays Sales and/or Trading desks, who are active market participants; https://www.cib.barclays/disclosures/barclays-global-markets-disclosures.html regarding our standard terms for Barclays Corporate and Investment Bank where we trade with you in principal-to-principal wholesale markets transactions; and in respect to Barclays Research, including disclosures relating to specific issuers, see: http://publicresearch.barclays.com. __________________________________________________________________________________ If you are incorporated or operating in Australia, read these important disclosures: https://www.cib.barclays/disclosures/important-disclosures-asia-pacific.html. __________________________________________________________________________________ For more details about how we use personal information, see our privacy notice: https://www.cib.barclays/disclosures/personal-information-use.html. __________________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
