The maven project doesn't have a code maven versions plugin, mojohaus formally codehaus has a versions-maven-plugin. Is that the plugin you're talking about? And I've just noticed they point their users mailing list to this maven users list.
1) What is the exact command line you are executing? something like this? $ mvn org.codehaus.mojo:versions-maven-plugin:2.7:display-dependency-updates 2) How many repo's do you point to? via your pom.xml or settings.xml As each repo will be checked separately which might be why the high execution time. The maven central calls might be say 10 mins but due to slow 'snapshots' it might take 50 mins. 3) Is the project public on github or similar? i.e. can i clone it myself and run the same command to see how long it takes for me? 4) Do you have a slow or high latency internet connection? As your email implices you might be in the Czech Republic. You might have a 25Mbps connection but if you have multiple users streaming 4K video and saturating the bandwidth it won't help you. 5) What location does repo1.maven.org resolve to? e.g. ping repo1.maven.org or nslookup repo1.maven.org. Then put the ip address into say https://ipinfo.io/ and see if that host is local to you... mine is resoling to a UK Data Center, yours might be going somewhere silly and non local 6) Maybe setup a nexus oss on your home/office/work network to cache this data closer. 7) See where the time is wasted, https://github.com/khmarbaise/maven-buildtime-profiler would help confirm where phases/goal/plugin is taking all the time, it might just show you what you know, which is the versions plugin is taking all the time. Hope some of the above is helpful or points towards the problem. Without knowing the exact command line you're using it is a little hard to help more. Also without seeing your pom or settings.xml as your output shows central and something called snapshots being polled. John On Sat, 11 Jul 2020 at 07:39, Lukáš Satin <lsa...@gpe.cz> wrote: > > Hi, > > Maven Versions Plugin scans whole Maven repository. > > It takes about 1 hour and scans everything from com.google.* and > org.springframework.* plus other packages while they are nowhere in the > pom.xml! There is only org.springbootframework.boot, org.apache.commons, > com.oracle! > > I read all articles, FAQ. > > Why is this behavior? How to make it update only actual dependencies > present in pom.xml and not some transitive stuff? > > [INFO] artifact com.google.api.grpc:proto-google-cloud-bigtable-v2: > checking for updates from snapshots > [INFO] artifact com.google.api.grpc:proto-google-cloud-billing-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:proto-google-cloud-billing-v1: checking > for updates from snapshots > [INFO] artifact com.google.api.grpc:grpc-google-cloud-billing-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:grpc-google-cloud-billing-v1: checking > for updates from snapshots > [INFO] artifact com.google.cloud:google-cloud-billing: checking for updates > from central > [INFO] artifact com.google.cloud:google-cloud-billing: checking for updates > from snapshots > [INFO] artifact > com.google.api.grpc:grpc-google-cloud-billingbudgets-v1beta1: checking for > updates from central > [INFO] artifact > com.google.api.grpc:grpc-google-cloud-billingbudgets-v1beta1: checking for > updates from snapshots > [INFO] artifact > com.google.api.grpc:proto-google-cloud-billingbudgets-v1beta1: checking for > updates from central > [INFO] artifact > com.google.api.grpc:proto-google-cloud-billingbudgets-v1beta1: checking for > updates from snapshots > [INFO] artifact com.google.cloud:google-cloud-billingbudgets: checking for > updates from central > [INFO] artifact com.google.cloud:google-cloud-billingbudgets: checking for > updates from snapshots > [INFO] artifact com.google.api.grpc:grpc-google-cloud-build-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:grpc-google-cloud-build-v1: checking > for updates from snapshots > [INFO] artifact com.google.api.grpc:proto-google-cloud-build-v1: checking > for updates from central > [INFO] artifact com.google.api.grpc:proto-google-cloud-build-v1: checking > for updates from snapshots > [INFO] artifact com.google.cloud:google-cloud-build: checking for updates > from central --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
