Re: Latest tag on maven-metadata.xml
Am 2020-07-22 um 19:08 schrieb Vinicius Scheidegger: Is Maven deploy plugin responsible to generate/update the latest tag on maven-metadata.xml? Not really, Maven Artifact Transfer is... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Latest tag on maven-metadata.xml
Is Maven deploy plugin responsible to generate/update the latest tag on maven-metadata.xml? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Versions Plugin scans whole Maven repository
I had the same issue a while back [1]. We now use use-latest-versions and no longer use properties for versions most of the time. Hth, [1] https://www.mail-archive.com/users@maven.apache.org/msg142064.html 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 Wed, Jul 22, 2020 at 2:27 PM Dennis Lundberg wrote: > Hi, > > This is most likely due to a dependency on something from Spring Boot. I > have seen this as well. In many of the Spring Boot POMs they declare a ton > of dependencies in dependency management, to make sure all their components > use the same versions. The versions-maven-plugin might go through all of > them, because they are transitive dependencies of Spring Boot, depending on > how the dependency on Spring Boot artifact is declared and which Spring > Boot artifact it is. > > -- > Dennis Lundberg > > > Den lör 11 juli 2020 kl 08:39 skrev Lukáš Satin : > > > 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 > > >
Re: Maven Versions Plugin scans whole Maven repository
Hi, This is most likely due to a dependency on something from Spring Boot. I have seen this as well. In many of the Spring Boot POMs they declare a ton of dependencies in dependency management, to make sure all their components use the same versions. The versions-maven-plugin might go through all of them, because they are transitive dependencies of Spring Boot, depending on how the dependency on Spring Boot artifact is declared and which Spring Boot artifact it is. -- Dennis Lundberg Den lör 11 juli 2020 kl 08:39 skrev Lukáš Satin : > 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 >
