I am trying to reproduce a build that was done a week ago. Our maven pom files
use range in many places ([1.0,1.1), when I go look at the pom of the published
project, it just shows the range, not the actual version chosen:
Published pom:
com.hp.cp.dfe.shared
common-types
I don't think you can.
The only way would be to use metadata from those GAV and see when it was
released/deployed.
Of if your don't use use " -ntp,--no-transfer-progress" AND a new workspace
per build AND have that log, then you would see what if downloads.
Or you use a local/company repository man
The Apache Maven team is pleased to announce the release of the Apache
Software Foundation Parent POM Version, version 26
https://maven.apache.org/pom/asf/
You should specify the version in your project as parent like the following:
org.apache
apache
26
You can download the appropriate
I don’t believe there currently is a way for this is native maven.
We ended up writing a custom tool/mojo for resolution management using a
DSL like:
repository https://repo1.maven.org/maven2/ as central;
resolve highest org.antlr:antlr4-maven-plugin:[4.10,5.0.0) via central;
locked org.antlr:
I know that might only help you in the future, but why don't you just
dump `mvn dependency:tree` into your build logs and maybe even attach it
to the artifact somewhere in META-INF/maven or so? I am co-maintaining
an OSS project which depends on another one using dependency version
ranges. We do no
