Re: mvn package command ends with error
The problem is that you are connecting to repos using HTTP rather than HTTPS, which is now blocked by default. This is new in Maven version 3.8.1. You can check out the release notes for more information including fixes and workarounds: https://maven.apache.org/docs/3.8.1/release-notes.html -- Andy Feldman On Mon, May 3, 2021 at 3:43 PM Compte Messagerie < informatique.e...@gmail.com> wrote: > hello, > i try to install dspace 6.3 on centos 8 with apache-maven-3.8.1 and > java-11.0.11 > when i start the command: > > $mvn package -X// for debug > it ends whith this error: > > [ERROR] Failed to execute goal on project solr: Could not resolve > dependencies for project org.dspace.modules:solr:war:6.3: Failed to collect > dependencies at org.dspace:dspace-solr:jar:classes:6.3 -> > org.apache.solr:solr-core:jar:4.10.4 -> > org.restlet.jee:org.restlet:jar:2.1.1: Failed to read artifact descriptor > for org.restlet.jee:org.restlet:jar:2.1.1: Could not transfer artifact > org.restlet.jee:org.restlet:pom:2.1.1 from/to maven-default-http-blocker ( > http://0.0.0.0/): Blocked mirror for repositories: [maven-snapshots ( > http://oss.sonatype.org/content/repositories/snapshots, default, > snapshots), maven-restlet (http://maven.restlet.org, default, > releases+snapshots), apache.snapshots ( > http://repository.apache.org/snapshots, default, disabled)] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal on project solr: Could not resolve dependencies for project > org.dspace.modules:solr:war:6.3: Failed to collect dependencies at > org.dspace:dspace-solr:jar:classes:6.3 -> > org.apache.solr:solr-core:jar:4.10.4 -> > org.restlet.jee:org.restlet:jar:2.1.1 > >
mvn package command ends with error
hello, i try to install dspace 6.3 on centos 8 with apache-maven-3.8.1 and java-11.0.11 when i start the command: $mvn package -X// for debug it ends whith this error: [ERROR] Failed to execute goal on project solr: Could not resolve dependencies for project org.dspace.modules:solr:war:6.3: Failed to collect dependencies at org.dspace:dspace-solr:jar:classes:6.3 -> org.apache.solr:solr-core:jar:4.10.4 -> org.restlet.jee:org.restlet:jar:2.1.1: Failed to read artifact descriptor for org.restlet.jee:org.restlet:jar:2.1.1: Could not transfer artifact org.restlet.jee:org.restlet:pom:2.1.1 from/to maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for repositories: [maven-snapshots (http://oss.sonatype.org/content/repositories/snapshots, default, snapshots), maven-restlet (http://maven.restlet.org, default, releases+snapshots), apache.snapshots (http://repository.apache.org/snapshots, default, disabled)] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project solr: Could not resolve dependencies for project org.dspace.modules:solr:war:6.3: Failed to collect dependencies at org.dspace:dspace-solr:jar:classes:6.3 -> org.apache.solr:solr-core:jar:4.10.4 -> org.restlet.jee:org.restlet:jar:2.1.1 at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:269) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:566) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project org.dspace.modules:solr:war:6.3: Failed to collect dependencies at org.dspace:dspace-solr:jar:classes:6.3 -> org.apache.solr:solr-core:jar:4.10.4 -> org.restlet.jee:org.restlet:jar:2.1.1 at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve (DefaultProjectDependenciesResolver.java:178) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:243) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (Lifecyc
pvn package command dependencies error
hello, i try to install dspace 6.3 on centos8 with apache-maven-3.8.1 and openjdk11 where i execute $mvn package -X//for debug it ends with: [INFO] --< org.dspace.modules:solr >--- [INFO] Building DSpace SOLR :: Local Customizations 6.3 [9/11] [INFO] [ war ]- [INFO] [INFO] Reactor Summary for DSpace Assembly and Configuration 6.3: [INFO] [INFO] DSpace Addon Modules ... SUCCESS [ 0.612 s] [INFO] DSpace Kernel :: Additions and Local Customizations SUCCESS [ 3.153 s] [INFO] DSpace XML-UI (Manakin) :: Local Customizations SUCCESS [03:51 min] [INFO] DSpace JSP-UI :: Local Customizations .. SUCCESS [02:12 min] [INFO] DSpace RDF :: Local Customizations . SUCCESS [03:20 min] [INFO] DSpace REST :: Local Customizations SUCCESS [02:22 min] [INFO] DSpace SWORD :: Local Customizations ... SUCCESS [03:08 min] [INFO] DSpace SWORD v2 :: Local Customizations SUCCESS [02:56 min] [INFO] DSpace SOLR :: Local Customizations FAILURE [ 0.209 s] [INFO] DSpace OAI-PMH :: Local Customizations . SKIPPED [INFO] DSpace Assembly and Configuration .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 17:56 min [INFO] Finished at: 2021-05-03T14:36:24+01:00 [INFO] [ERROR] Failed to execute goal on project solr: Could not resolve dependencies for project org.dspace.modules:solr:war:6.3: Failed to collect dependencies at org.dspace:dspace-solr:jar:classes:6.3 -> org.apache.solr:solr-core:jar:4.10.4 -> org.restlet.jee:org.restlet:jar:2.1.1: Failed to read artifact descriptor for org.restlet.jee:org.restlet:jar:2.1.1: Could not transfer artifact org.restlet.jee:org.restlet:pom:2.1.1 from/to maven-default-http-blocker ( http://0.0.0.0/): Blocked mirror for repositories: [maven-snapshots ( http://oss.sonatype.org/content/repositories/snapshots, default, snapshots), maven-restlet (http://maven.restlet.org, default, releases+snapshots), apache.snapshots ( http://repository.apache.org/snapshots, default, disabled)] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project solr: Could not resolve dependencies for project org.dspace.modules:solr:war:6.3: Failed to collect dependencies at org.dspace:dspace-solr:jar:classes:6.3 -> org.apache.solr:solr-core:jar:4.10.4 -> org.restlet.jee:org.restlet:jar:2.1.1 at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies (LifecycleDependencyResolver.java:269) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies (LifecycleDependencyResolver.java:147) at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved (MojoExecutor.java:248) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:202) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:566) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) Caused by
Re: Trying out new verbose dependency tree: very slow result
Sorry for the double post, but I also see that strange jaspersoft repository in Andy's debug log. EBUG] Writing tracking file /Users/andyf/.m2/repository/xm l-apis/xml-apis/1.3.02/_remote.repositories [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repository.apache.org/snapshots [DEBUG] Using transporter WagonTransporter with priority -1.0 for http://www.jasperforge.org/maven2 [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://oss.sonatype.org/content/repositories/snapshots [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://www.jasperforge.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repository.apache.org/snapshots [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://oss.sonatype.org/content/repositories/snapshots [DEBUG] Redirect requested to location ' https://www.jasperforge.org/maven2/eclipse/jdtcore/maven-metadata.xml' 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 Mon, May 3, 2021 at 9:50 PM Nick Stolwijk wrote: > And when I look at the dependency tree of the maven-dependency-plugin I > don't see the dependencies that are checked there. > > > [DEBUG] Writing tracking file /Users/andyf/.m2/repository/xa > lan/xalan/2.7.0/_remote.repositories > > [DEBUG] Verifying availability of > > /Users/andyf/.m2/repository/xalan/xalan/2.7.2/xalan-2.7.2.pom > from > > mvn dependency:tree -Dincludes=xalan > [INFO] Scanning for projects... > [INFO] > [INFO] --< org.apache.maven.plugins:maven-dependency-plugin > >-- > [INFO] Building Apache Maven Dependency Plugin 3.1.4-SNAPSHOT > [INFO] [ maven-plugin > ] > [INFO] > [INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ > maven-dependency-plugin --- > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 1.917 s > [INFO] Finished at: 2021-05-03T21:47:34+02:00 > > So why is the new SNAPSHOT of the Maven Dependency Tree checking > dependencies that are not in the dependency tree? > > With regards, > > 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 Mon, May 3, 2021 at 9:38 PM Andy Feldman wrote: > >> I'm seeing the slowness as well. To avoid confusion about whether my own >> repos have some unusual configuration, I ran it against the >> maven-dependency-plugin repo itself, as cloned today. The debug logs (-X) >> contained many entries like this: >> >> [...] >> [DEBUG] Using transporter WagonTransporter with priority -1.0 for >> https://repo.maven.apache.org/maven2 >> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for >> https://repo.maven.apache.org/maven2 >> [DEBUG] Writing tracking file >> /Users/andyf/.m2/repository/xalan/xalan/2.7.0/_remote.repositories >> [DEBUG] Verifying availability of >> /Users/andyf/.m2/repository/xalan/xalan/2.7.2/xalan-2.7.2.pom from >> [apache.snapshots (https://repository.apache.org/snapshots, default, >> snapshots), central (https://repo.maven.apache.org/maven2, default, >> releases), sonatype-nexus-snapshots ( >> https://oss.sonatype.org/content/repositories/snapshots, default, >> snapshots), jaspersoft (http://www.jasperforge.org/maven2, default, >> releases+snapshots)] >> [DEBUG] Using transporter WagonTransporter with priority -1.0 for >> https://repo.maven.apache.org/maven2 >> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for >> https://repo.maven.apache.org/maven2 >> [DEBUG] Writing tracking file >> /Users/andyf/.m2/repository/xalan/xalan/2.7.2/_remote.repositories >> [DEBUG] Verifying availability of >> /Users/andyf/.m2/repository/xalan/serializer/2.7.2/serializer-2.7.2.pom >> from [apache.snapshots (https://repository.apache.org/snapshots, default, >> snapshots), central (https://repo.maven.apache.org/maven2, default, >> releases), sonatype-nexus-snapshots ( >> https://oss.sonatype.org/content/repositories/snapshots, default, >> snapshots), jaspersoft (http://www.jasperforge.org/maven2, default, >> releases+snapshots)] >> [DEBUG] Using transporter WagonTransporter with priority -1.0 for >> https://repo.maven.apache.org/maven2 >> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for >> https:/
Re: Trying out new verbose dependency tree: very slow result
And when I look at the dependency tree of the maven-dependency-plugin I don't see the dependencies that are checked there. > [DEBUG] Writing tracking file /Users/andyf/.m2/repository/xa lan/xalan/2.7.0/_remote.repositories > [DEBUG] Verifying availability of > /Users/andyf/.m2/repository/xalan/xalan/2.7.2/xalan-2.7.2.pom from mvn dependency:tree -Dincludes=xalan [INFO] Scanning for projects... [INFO] [INFO] --< org.apache.maven.plugins:maven-dependency-plugin >-- [INFO] Building Apache Maven Dependency Plugin 3.1.4-SNAPSHOT [INFO] [ maven-plugin ] [INFO] [INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ maven-dependency-plugin --- [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1.917 s [INFO] Finished at: 2021-05-03T21:47:34+02:00 So why is the new SNAPSHOT of the Maven Dependency Tree checking dependencies that are not in the dependency tree? With regards, 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 Mon, May 3, 2021 at 9:38 PM Andy Feldman wrote: > I'm seeing the slowness as well. To avoid confusion about whether my own > repos have some unusual configuration, I ran it against the > maven-dependency-plugin repo itself, as cloned today. The debug logs (-X) > contained many entries like this: > > [...] > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Writing tracking file > /Users/andyf/.m2/repository/xalan/xalan/2.7.0/_remote.repositories > [DEBUG] Verifying availability of > /Users/andyf/.m2/repository/xalan/xalan/2.7.2/xalan-2.7.2.pom from > [apache.snapshots (https://repository.apache.org/snapshots, default, > snapshots), central (https://repo.maven.apache.org/maven2, default, > releases), sonatype-nexus-snapshots ( > https://oss.sonatype.org/content/repositories/snapshots, default, > snapshots), jaspersoft (http://www.jasperforge.org/maven2, default, > releases+snapshots)] > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Writing tracking file > /Users/andyf/.m2/repository/xalan/xalan/2.7.2/_remote.repositories > [DEBUG] Verifying availability of > /Users/andyf/.m2/repository/xalan/serializer/2.7.2/serializer-2.7.2.pom > from [apache.snapshots (https://repository.apache.org/snapshots, default, > snapshots), central (https://repo.maven.apache.org/maven2, default, > releases), sonatype-nexus-snapshots ( > https://oss.sonatype.org/content/repositories/snapshots, default, > snapshots), jaspersoft (http://www.jasperforge.org/maven2, default, > releases+snapshots)] > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Writing tracking file > /Users/andyf/.m2/repository/xalan/serializer/2.7.2/_remote.repositories > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Writing tracking file > /Users/andyf/.m2/repository/xml-apis/xml-apis/1.3.02/_remote.repositories > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > https://repository.apache.org/snapshots > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > http://www.jasperforge.org/maven2 > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Using transporter WagonTransporter with priority -1.0 for > https://oss.sonatype.org/content/repositories/snapshots > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > https://repo.maven.apache.org/maven2 > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > http://www.jasperforge.org/maven2 > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > https://repository.apache.org/snapshots > [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for > https://oss.sonatype.org/content/repositories/snapshots > [DEBUG] Redirect requested to location ' > https://www.jasperforge.org/maven2/eclipse/jdtcore/maven-metadata.xml' > [DEBUG] Writing tracking file > /Users/andyf/.m2/repository/eclipse/jdtcore/resolver-status.properties > [DEBU
Re: Getting version upgrade advise to upgrade a BOM..
If your bom version is in a property you must run display-properties-update instead https://www.mojohaus.org/versions-maven-plugin/display-property-updates-mojo.html -- http://bernd.eckenfels.net Von: Niels Basjes Gesendet: Monday, May 3, 2021 1:26:58 PM An: Maven Users List Betreff: Re: Getting version upgrade advise to upgrade a BOM.. Hi, Update: I did some experiments to see how all of this works right now. If I do this in my test project (with a few extra deliberately placed 'old' dependencies) * mvn versions:display-dependency-updates versions:display-plugin-updates* I get - All the dependencies inside the google libraries-bom that need to be updated (like grpc). - I do *not* get a hint to update the libraries-bom itself. - The hint to update this dependency : org.slf4j:slf4j-api . 1.7.25 -> 1.7.30 - The hint to update this test dependency: junit:junit ... 4.13 -> 4.13.2 - The hint to update this plugin: org.sonarsource.scanner.maven:sonar-maven-plugin 3.8.0.2131 -> 3.9.0.2155 If I run the mentioned * mvn versions:use-latest-versions versions:update-properties -DgenerateBackupPoms=false* The ONLY thing that has been updated is the libraries-bom version (in a property) None of the things mentioned in the previous command have been changed or mentioned. I had a quick look at the manual of this version plugin and even tried this (with no changes) *mvn versions:use-latest-releases versions:use-releases versions:use-latest-versions versions:update-properties -DgenerateBackupPoms=false* What am I doing wrong here? Niels Basjes On Sun, May 2, 2021 at 4:38 PM Niels Basjes wrote: > Thanks, > > This actually works. > I find this surprising because apparently this plugin cannot indicate what > needs to be changed, but it can do the change. > > Niels > > On Sun, May 2, 2021 at 4:25 PM Nick Stolwijk > wrote: > >> To update the BOM dependencies you can use the Maven versions plugin: >> >> mvn versions:use-latest-versions versions:update-properties >> -DgenerateBackupPoms=false >> >> 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 Sun, May 2, 2021 at 3:12 PM Niels Basjes wrote: >> >> > Hi, >> > >> > Thanks for the suggestion. >> > Apparently the "standard" maven versions plugin does not do this >> correctly >> > yet. >> > >> > I was looking at this renovate tool yet what I found is that it seems to >> > only support creating pull/merge requests. >> > This is very nice but not what I want right now. >> > Is there a way to run it locally (without any github/gitlab/... system) >> and >> > generate a patch file or just a list of problematic versions? >> > >> > Niels Basjes >> > >> > >> > On Fri, Apr 30, 2021 at 3:40 AM Tomo Suzuki > > >> > wrote: >> > >> > > Hi Niels, >> > > (Thank you for using the libraries-bom! I'm one of the maintainers of >> the >> > > BOM.) >> > > >> > > I don't know how to do it in Maven. However, I often see people using >> > > dependabot or >> > > renovatebot integrated with their repositories. >> > > An example pull request by renovatebot: >> > > https://github.com/googleapis/java-securitycenter/pull/472 >> > > >> > > Note that RenovateBot doesn't require GitHub.com repository: >> > > https://github.com/renovatebot/renovate#self-hosting >> > > >> > > >> > > >> > > >> > > On Thu, Apr 29, 2021 at 5:12 PM Delany >> > wrote: >> > > >> > > > Is it this >> > https://github.com/mojohaus/versions-maven-plugin/issues/395 >> > > > Regards, >> > > > Delany >> > > > >> > > > >> > > > On Thu, 29 Apr 2021, 22:22 Niels Basjes, wrote: >> > > > >> > > > > Hi, >> > > > > >> > > > > I see quite a few situations where the dependencies for toolkit >> are >> > > > > provided in the form of a dependency you must "import" in >> > > > > the dependencyManagement section. >> > > > > They provide this to ensure you always have a working combination >> > for a >> > > > lot >> > > > > of closely related dependencies. >> > > > > >> > > > > To illustrate the problem I ran into I created this minimal >> pom.xml: >> > > > > >> > > > > >> > > > > http://maven.apache.org/POM/4.0.0"; >> > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> > > > > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> > > > > http://maven.apache.org/xsd/maven-4.0.0.xsd";> >> > > > > 4.0.0 >> > > > > >> > > > > nl.basjes.example >> > > > > dependency-version-test >> > > > > 0.1-SNAPSHOT >> > > > > jar >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > com.google.cloud >> > > > > libraries-bom >> > > > > 19.0.0 >> > >
Re: Trying out new verbose dependency tree: very slow result
I'm seeing the slowness as well. To avoid confusion about whether my own repos have some unusual configuration, I ran it against the maven-dependency-plugin repo itself, as cloned today. The debug logs (-X) contained many entries like this: [...] [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Writing tracking file /Users/andyf/.m2/repository/xalan/xalan/2.7.0/_remote.repositories [DEBUG] Verifying availability of /Users/andyf/.m2/repository/xalan/xalan/2.7.2/xalan-2.7.2.pom from [apache.snapshots (https://repository.apache.org/snapshots, default, snapshots), central (https://repo.maven.apache.org/maven2, default, releases), sonatype-nexus-snapshots ( https://oss.sonatype.org/content/repositories/snapshots, default, snapshots), jaspersoft (http://www.jasperforge.org/maven2, default, releases+snapshots)] [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Writing tracking file /Users/andyf/.m2/repository/xalan/xalan/2.7.2/_remote.repositories [DEBUG] Verifying availability of /Users/andyf/.m2/repository/xalan/serializer/2.7.2/serializer-2.7.2.pom from [apache.snapshots (https://repository.apache.org/snapshots, default, snapshots), central (https://repo.maven.apache.org/maven2, default, releases), sonatype-nexus-snapshots ( https://oss.sonatype.org/content/repositories/snapshots, default, snapshots), jaspersoft (http://www.jasperforge.org/maven2, default, releases+snapshots)] [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Writing tracking file /Users/andyf/.m2/repository/xalan/serializer/2.7.2/_remote.repositories [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Writing tracking file /Users/andyf/.m2/repository/xml-apis/xml-apis/1.3.02/_remote.repositories [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repository.apache.org/snapshots [DEBUG] Using transporter WagonTransporter with priority -1.0 for http://www.jasperforge.org/maven2 [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://oss.sonatype.org/content/repositories/snapshots [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for http://www.jasperforge.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repository.apache.org/snapshots [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://oss.sonatype.org/content/repositories/snapshots [DEBUG] Redirect requested to location ' https://www.jasperforge.org/maven2/eclipse/jdtcore/maven-metadata.xml' [DEBUG] Writing tracking file /Users/andyf/.m2/repository/eclipse/jdtcore/resolver-status.properties [DEBUG] Writing tracking file /Users/andyf/.m2/repository/eclipse/jdtcore/resolver-status.properties [DEBUG] Redirect requested to location ' https://community.jaspersoft.com/maven2/eclipse/jdtcore/maven-metadata.xml' [DEBUG] Writing tracking file /Users/andyf/.m2/repository/eclipse/jdtcore/resolver-status.properties [DEBUG] Writing tracking file /Users/andyf/.m2/repository/eclipse/jdtcore/resolver-status.properties [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Writing tracking file /Users/andyf/.m2/repository/eclipse/jdtcore/3.1.0/_remote.repositories [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Writing tracking file /Users/andyf/.m2/repository/eclipse/jdtcore/3.2.0.v_658/_remote.repositories [DEBUG] Using transporter WagonTransporter with priority -1.0 for https://repo.maven.apache.org/maven2 [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for https://repo.maven.apache.org/maven2 [DEBUG] Writing tracking file /Users/andyf/.m2/repository/groovy/groovy-all-minimal/1.0/_remote.repositories [...] I took a stack dump with jstack a few times and it was basically the same each time. The relevant section of the main thread's stack (the part with dependency-plug
Re: Trying out new verbose dependency tree: very slow result
Hi Enrico, I am already on Maven 3.8.1. I tried to build the maven-dependency-plugin and my own simple project with a fresh repository and it took way less time this time. Alas, it still uses some repositories I didn't include. Also, it fails with an exception. My settings.xml only contains the repositories in my company Nexus which holds the company parent pom (without repositories) and our testtools bom (importing some test utilities like JUnit BOM, but my project only uses few dependencies from there). Questions: - Why is it way faster with a clean repository than a dirty one? I build the same project with few dependencies. - Where are those repositories (https://www.jasperforge.org, https://repository.apache.org/snapshots - Where is the exception coming from? (java.lang.IllegalArgumentException: Malformed \u encoding.) (Relevant) output: 15:19:52 $ mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.4-SNAPSHOT:tree -Dverbose=true -s settings.xml -X Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) Maven home: C:\ProgramData\chocolatey\lib\maven\apache-maven-3.8.1 Java version: 16.0.1, vendor: Oracle Corporation, runtime: C:\Program Files\OpenJDK\jdk-16.0.1 Default locale: en_GB, platform encoding: UTF-8 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" [INFO] Error stacktraces are turned on. [DEBUG] Message scheme: color [DEBUG] Message styles: debug info warning error success failure strong mojo project [DEBUG] Reading global settings from C:\ProgramData\chocolatey\lib\maven\apache-maven-3.8.1\conf\settings.xml [DEBUG] Reading user settings from C:\work\BIB\utilities_commons-lang\settings.xml [DEBUG] Reading global toolchains from C:\ProgramData\chocolatey\lib\maven\apache-maven-3.8.1\conf\toolchains.xml [DEBUG] Reading user toolchains from C:\Users\nicks\.m2\toolchains.xml [DEBUG] Using local repository at c:\repo [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for c:\repo [INFO] Scanning for projects... [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for apache.snapshots (http://repository.apache.org/snapshots). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for codehaus.snapshots (http://snapshots.repository.codehaus.org). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for repository.jboss.org (http://repository.jboss.org/maven2). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for snapshots.jboss.org (http://snapshots.jboss.org/maven2). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for oss.sonatype.org/jboss-snapshots ( http://oss.sonatype.org/content/repositories/jboss-snapshots). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for snapshots (http://snapshots.maven.codehaus.org/maven2). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for central (http://repo1.maven.org/maven2). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for apache-snapshots (http://people.apache.org/maven-snapshot-repository). [DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for codehaus-snapshots (http://snapshots.repository.codehaus.org). ...[INFO] < com.example.bibliotheek.utilities:commons-lang >- [INFO] Building Bibliotheek - Commons-Lang 1.5.2-SNAPSHOT [INFO] ---[ bundle ]--- [DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy] [DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean] [DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy] [DEBUG] === PROJECT BUILD PLAN [DEBUG] Project: com.example.bibliotheek.utilities:commons-lang:1.5.2-SNAPSHOT [DEBUG] Dependencies (collect): [test] [DEBUG] Dependencies (resolve): [] [DEBUG] Repositories (dependencies): [sde-releases ( https://nexus.example.com/repository/sde-releases/, default, releases), sde-snapshots (https://nexus.example.com/repository/sde-snapshots/, default, snapshots), shared-releases ( https://nexus.example.com/repository/shared-releases/, default, releases), shared-snapshots (https://nexus.example.com/repository/shared-snapshots/, default, snapshots), central (https://repo.maven.apache.org/maven2, default, releases)] [DEBUG] Repositories (plugins) : [central ( https://repo.maven.apache.org/maven2, default, releases)] [DEBUG] ---
Re: Trying out new verbose dependency tree: very slow result
Il giorno lun 3 mag 2021 alle ore 14:14 Nick Stolwijk
ha scritto:
>
> Hi Enrico,
>
> I did a search and replace on our domain name. The Nexus instance at our
> company is a mirror for Maven Central.
>
> And it is the only repository used in the build. See the output for
> list-repositories in the last mail.
I also see these repo:
http://www.jasperforge.org/maven2
https://repository.apache.org/snapshots
https://community.jaspersoft.com/maven2
off topic: you can try to upgrade to Maven 3.8.1 in order to skip
accesses to non-https repositories and to pick up a few enhancements
about Repository management.
Enrico
>
> 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 Mon, May 3, 2021 at 2:02 PM Enrico Olivelli wrote:
>
> > Il giorno lun 3 mag 2021 alle ore 13:56 Nick Stolwijk
> > ha scritto:
> > >
> > > Hi Enrico,
> > >
> > > It looks like it is trying to update the world while using repositories I
> > > can't explain. ;-)
> >
> > Do you have references to several third party repositories ?
> >
> > it looks like https://nexus.example.com is not a good repo
> >
> > Enrico
> >
> > >
> > > [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:list-repositories
> > > (default-cli) @ commons-lang ---
> > > Downloading from public_nx3:
> > >
> > https://nexus.example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
> > > Downloaded from public_nx3: https://nexus.
> > >
> > example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
> > > (1.7 kB at 1.9 kB/s)
> > > [INFO] Repositories used by this build:
> > > [INFO]id: public_nx3
> > > url: https://nexus.example.com/repository/public/
> > >layout: default
> > > snapshots: [enabled => true, update => daily]
> > > releases: [enabled => true, update => daily]
> > >
> > > Output of Maven debug:
> > >
> > > [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:tree (default-cli) @
> > > commons-lang ---
> > > [DEBUG] Using mirror public_nx3 (
> > > https://nexus.example.com/repository/public/) for apache.snapshots (
> > > http://people.apache.org/maven-snapshot-repository).
> > > [DEBUG] Using mirror public_nx3 (
> > > https://nexus.example.com/repository/public/) for ow2-snapshot (
> > > http://repository.ow2.org/nexus/content/repositories/snapshots).
> > > [DEBUG] Dependency collection stats {ConflictMarker.analyzeTime=569300,
> > > ConflictMarker.markTime=273500, ConflictMarker.nodeCount=434,
> > > ConflictIdSorter.graphTime=329300, ConflictIdSorter.topsortTime=63200,
> > > ConflictIdSorter.conflictIdCount=93,
> > > ConflictIdSorter.conflictIdCycleCount=0,
> > > ConflictResolver.totalTime=2936900,
> > ConflictResolver.conflictItemCount=194,
> > > DefaultDependencyCollector.collectTime=347565200,
> > > DefaultDependencyCollector.transformTime=4219500}
> > > [DEBUG]
> > org.apache.maven.plugins:maven-dependency-plugin:jar:3.1.4-SNAPSHOT
> > > [DEBUG]org.apache.maven:maven-artifact:jar:3.1.1:compile
> > > [DEBUG]org.apache.maven:maven-plugin-api:jar:3.1.1:compile
> > > [DEBUG]
> > org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.0.0.M5:compile
> > > [DEBUG] javax.enterprise:cdi-api:jar:1.0:compile
> > > [DEBUG] javax.annotation:jsr250-api:jar:1.0:compile
> > > [DEBUG] javax.inject:javax.inject:jar:1:compile
> > > [DEBUG] com.google.guava:guava:jar:10.0.1:compile
> > > [DEBUG] com.google.code.findbugs:jsr305:jar:1.3.9:compile
> > > [DEBUG] org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0:compile
> > > [DEBUG] aopalliance:aopalliance:jar:1.0:compile
> > > [DEBUG]
> > > org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.0.0.M5:compile
> > > [DEBUG]org.apache.maven:maven-model:jar:3.1.1:compile
> > > [DEBUG]org.apache.maven:maven-core:jar:3.1.1:compile
> > > [DEBUG] org.apache.maven:maven-settings-builder:jar:3.1.1:compile
> > > [DEBUG] org.apache.maven:maven-model-builder:jar:3.1.1:compile
> > > [DEBUG] org.eclipse.aether:aether-impl:jar:0.9.0.M2:compile
> > > [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.19:compile
> > > [DEBUG] org.codehaus.plexus:plexus-classworlds:jar:2.5.1:compile
> > > [DEBUG]
> > > org.codehaus.plexus:plexus-component-annotations:jar:2.0.0:compile
> > (version
> > > managed from default)
> > > [DEBUG] org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile
> > > [DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.4:compile
> > > [DEBUG]org.apache.maven:maven-repository-metadata:jar:3.1.1:compile
> > > [DEBUG]org.apache.maven:maven-settings:jar:3.1.1:compile
> > > [DEBUG]org.apache.maven:maven-aether-provider:jar:3.1.1:compile
> > > [DEBUG] org.eclipse.aether:aether-spi:
Re: Trying out new verbose dependency tree: very slow result
Hi Enrico,
I did a search and replace on our domain name. The Nexus instance at our
company is a mirror for Maven Central.
And it is the only repository used in the build. See the output for
list-repositories in the last mail.
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 Mon, May 3, 2021 at 2:02 PM Enrico Olivelli wrote:
> Il giorno lun 3 mag 2021 alle ore 13:56 Nick Stolwijk
> ha scritto:
> >
> > Hi Enrico,
> >
> > It looks like it is trying to update the world while using repositories I
> > can't explain. ;-)
>
> Do you have references to several third party repositories ?
>
> it looks like https://nexus.example.com is not a good repo
>
> Enrico
>
> >
> > [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:list-repositories
> > (default-cli) @ commons-lang ---
> > Downloading from public_nx3:
> >
> https://nexus.example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
> > Downloaded from public_nx3: https://nexus.
> >
> example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
> > (1.7 kB at 1.9 kB/s)
> > [INFO] Repositories used by this build:
> > [INFO]id: public_nx3
> > url: https://nexus.example.com/repository/public/
> >layout: default
> > snapshots: [enabled => true, update => daily]
> > releases: [enabled => true, update => daily]
> >
> > Output of Maven debug:
> >
> > [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:tree (default-cli) @
> > commons-lang ---
> > [DEBUG] Using mirror public_nx3 (
> > https://nexus.example.com/repository/public/) for apache.snapshots (
> > http://people.apache.org/maven-snapshot-repository).
> > [DEBUG] Using mirror public_nx3 (
> > https://nexus.example.com/repository/public/) for ow2-snapshot (
> > http://repository.ow2.org/nexus/content/repositories/snapshots).
> > [DEBUG] Dependency collection stats {ConflictMarker.analyzeTime=569300,
> > ConflictMarker.markTime=273500, ConflictMarker.nodeCount=434,
> > ConflictIdSorter.graphTime=329300, ConflictIdSorter.topsortTime=63200,
> > ConflictIdSorter.conflictIdCount=93,
> > ConflictIdSorter.conflictIdCycleCount=0,
> > ConflictResolver.totalTime=2936900,
> ConflictResolver.conflictItemCount=194,
> > DefaultDependencyCollector.collectTime=347565200,
> > DefaultDependencyCollector.transformTime=4219500}
> > [DEBUG]
> org.apache.maven.plugins:maven-dependency-plugin:jar:3.1.4-SNAPSHOT
> > [DEBUG]org.apache.maven:maven-artifact:jar:3.1.1:compile
> > [DEBUG]org.apache.maven:maven-plugin-api:jar:3.1.1:compile
> > [DEBUG]
> org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.0.0.M5:compile
> > [DEBUG] javax.enterprise:cdi-api:jar:1.0:compile
> > [DEBUG] javax.annotation:jsr250-api:jar:1.0:compile
> > [DEBUG] javax.inject:javax.inject:jar:1:compile
> > [DEBUG] com.google.guava:guava:jar:10.0.1:compile
> > [DEBUG] com.google.code.findbugs:jsr305:jar:1.3.9:compile
> > [DEBUG] org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0:compile
> > [DEBUG] aopalliance:aopalliance:jar:1.0:compile
> > [DEBUG]
> > org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.0.0.M5:compile
> > [DEBUG]org.apache.maven:maven-model:jar:3.1.1:compile
> > [DEBUG]org.apache.maven:maven-core:jar:3.1.1:compile
> > [DEBUG] org.apache.maven:maven-settings-builder:jar:3.1.1:compile
> > [DEBUG] org.apache.maven:maven-model-builder:jar:3.1.1:compile
> > [DEBUG] org.eclipse.aether:aether-impl:jar:0.9.0.M2:compile
> > [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.19:compile
> > [DEBUG] org.codehaus.plexus:plexus-classworlds:jar:2.5.1:compile
> > [DEBUG]
> > org.codehaus.plexus:plexus-component-annotations:jar:2.0.0:compile
> (version
> > managed from default)
> > [DEBUG] org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile
> > [DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.4:compile
> > [DEBUG]org.apache.maven:maven-repository-metadata:jar:3.1.1:compile
> > [DEBUG]org.apache.maven:maven-settings:jar:3.1.1:compile
> > [DEBUG]org.apache.maven:maven-aether-provider:jar:3.1.1:compile
> > [DEBUG] org.eclipse.aether:aether-spi:jar:0.9.0.M2:compile
> > [DEBUG]org.apache.maven.reporting:maven-reporting-api:jar:3.0:compile
> > [DEBUG]
> org.apache.maven.reporting:maven-reporting-impl:jar:3.0.0:compile
> > [DEBUG]
> > org.apache.maven.doxia:doxia-decoration-model:jar:1.7.4:compile
> > [DEBUG]commons-io:commons-io:jar:2.6:compile
> > [DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.9.1:compile
> > [DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.9.1:compile
> > [DEBUG]org.apache.maven.doxia:doxia-core:jar:1.9.1:compile
> > [DEBUG]
> org.codehaus.plexus:plexus-container-d
Re: Trying out new verbose dependency tree: very slow result
Il giorno lun 3 mag 2021 alle ore 13:56 Nick Stolwijk
ha scritto:
>
> Hi Enrico,
>
> It looks like it is trying to update the world while using repositories I
> can't explain. ;-)
Do you have references to several third party repositories ?
it looks like https://nexus.example.com is not a good repo
Enrico
>
> [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:list-repositories
> (default-cli) @ commons-lang ---
> Downloading from public_nx3:
> https://nexus.example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
> Downloaded from public_nx3: https://nexus.
> example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
> (1.7 kB at 1.9 kB/s)
> [INFO] Repositories used by this build:
> [INFO]id: public_nx3
> url: https://nexus.example.com/repository/public/
>layout: default
> snapshots: [enabled => true, update => daily]
> releases: [enabled => true, update => daily]
>
> Output of Maven debug:
>
> [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:tree (default-cli) @
> commons-lang ---
> [DEBUG] Using mirror public_nx3 (
> https://nexus.example.com/repository/public/) for apache.snapshots (
> http://people.apache.org/maven-snapshot-repository).
> [DEBUG] Using mirror public_nx3 (
> https://nexus.example.com/repository/public/) for ow2-snapshot (
> http://repository.ow2.org/nexus/content/repositories/snapshots).
> [DEBUG] Dependency collection stats {ConflictMarker.analyzeTime=569300,
> ConflictMarker.markTime=273500, ConflictMarker.nodeCount=434,
> ConflictIdSorter.graphTime=329300, ConflictIdSorter.topsortTime=63200,
> ConflictIdSorter.conflictIdCount=93,
> ConflictIdSorter.conflictIdCycleCount=0,
> ConflictResolver.totalTime=2936900, ConflictResolver.conflictItemCount=194,
> DefaultDependencyCollector.collectTime=347565200,
> DefaultDependencyCollector.transformTime=4219500}
> [DEBUG] org.apache.maven.plugins:maven-dependency-plugin:jar:3.1.4-SNAPSHOT
> [DEBUG]org.apache.maven:maven-artifact:jar:3.1.1:compile
> [DEBUG]org.apache.maven:maven-plugin-api:jar:3.1.1:compile
> [DEBUG] org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.0.0.M5:compile
> [DEBUG] javax.enterprise:cdi-api:jar:1.0:compile
> [DEBUG] javax.annotation:jsr250-api:jar:1.0:compile
> [DEBUG] javax.inject:javax.inject:jar:1:compile
> [DEBUG] com.google.guava:guava:jar:10.0.1:compile
> [DEBUG] com.google.code.findbugs:jsr305:jar:1.3.9:compile
> [DEBUG] org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0:compile
> [DEBUG] aopalliance:aopalliance:jar:1.0:compile
> [DEBUG]
> org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.0.0.M5:compile
> [DEBUG]org.apache.maven:maven-model:jar:3.1.1:compile
> [DEBUG]org.apache.maven:maven-core:jar:3.1.1:compile
> [DEBUG] org.apache.maven:maven-settings-builder:jar:3.1.1:compile
> [DEBUG] org.apache.maven:maven-model-builder:jar:3.1.1:compile
> [DEBUG] org.eclipse.aether:aether-impl:jar:0.9.0.M2:compile
> [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.19:compile
> [DEBUG] org.codehaus.plexus:plexus-classworlds:jar:2.5.1:compile
> [DEBUG]
> org.codehaus.plexus:plexus-component-annotations:jar:2.0.0:compile (version
> managed from default)
> [DEBUG] org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile
> [DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.4:compile
> [DEBUG]org.apache.maven:maven-repository-metadata:jar:3.1.1:compile
> [DEBUG]org.apache.maven:maven-settings:jar:3.1.1:compile
> [DEBUG]org.apache.maven:maven-aether-provider:jar:3.1.1:compile
> [DEBUG] org.eclipse.aether:aether-spi:jar:0.9.0.M2:compile
> [DEBUG]org.apache.maven.reporting:maven-reporting-api:jar:3.0:compile
> [DEBUG]org.apache.maven.reporting:maven-reporting-impl:jar:3.0.0:compile
> [DEBUG]
> org.apache.maven.doxia:doxia-decoration-model:jar:1.7.4:compile
> [DEBUG]commons-io:commons-io:jar:2.6:compile
> [DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.9.1:compile
> [DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.9.1:compile
> [DEBUG]org.apache.maven.doxia:doxia-core:jar:1.9.1:compile
> [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.7.1:compile
> [DEBUG] org.apache.xbean:xbean-reflect:jar:3.7:compile
> [DEBUG] com.google.collections:google-collections:jar:1.0:compile
> [DEBUG] org.apache.httpcomponents:httpclient:jar:4.5.8:compile
> [DEBUG] commons-logging:commons-logging:jar:1.2:compile
> [DEBUG] commons-codec:commons-codec:jar:1.11:compile
> [DEBUG] org.apache.httpcomponents:httpcore:jar:4.4.11:compile
> [DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.9.2:compile
> [DEBUG] org.apache.maven.doxia:doxia-skin-model:jar:1.9.2:compile
> [DEBUG] org.apache.maven.doxia:doxia-module-xhtml:jar:1.9.1:compile
> [DEBUG] org.apache.maven.
Re: Trying out new verbose dependency tree: very slow result
Hi Enrico,
It looks like it is trying to update the world while using repositories I
can't explain. ;-)
[INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:list-repositories
(default-cli) @ commons-lang ---
Downloading from public_nx3:
https://nexus.example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
Downloaded from public_nx3: https://nexus.
example.com/repository/public/com/example/bibliotheek/utilities/commons-lang/1.5.2-SNAPSHOT/maven-metadata.xml
(1.7 kB at 1.9 kB/s)
[INFO] Repositories used by this build:
[INFO]id: public_nx3
url: https://nexus.example.com/repository/public/
layout: default
snapshots: [enabled => true, update => daily]
releases: [enabled => true, update => daily]
Output of Maven debug:
[INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:tree (default-cli) @
commons-lang ---
[DEBUG] Using mirror public_nx3 (
https://nexus.example.com/repository/public/) for apache.snapshots (
http://people.apache.org/maven-snapshot-repository).
[DEBUG] Using mirror public_nx3 (
https://nexus.example.com/repository/public/) for ow2-snapshot (
http://repository.ow2.org/nexus/content/repositories/snapshots).
[DEBUG] Dependency collection stats {ConflictMarker.analyzeTime=569300,
ConflictMarker.markTime=273500, ConflictMarker.nodeCount=434,
ConflictIdSorter.graphTime=329300, ConflictIdSorter.topsortTime=63200,
ConflictIdSorter.conflictIdCount=93,
ConflictIdSorter.conflictIdCycleCount=0,
ConflictResolver.totalTime=2936900, ConflictResolver.conflictItemCount=194,
DefaultDependencyCollector.collectTime=347565200,
DefaultDependencyCollector.transformTime=4219500}
[DEBUG] org.apache.maven.plugins:maven-dependency-plugin:jar:3.1.4-SNAPSHOT
[DEBUG]org.apache.maven:maven-artifact:jar:3.1.1:compile
[DEBUG]org.apache.maven:maven-plugin-api:jar:3.1.1:compile
[DEBUG] org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.0.0.M5:compile
[DEBUG] javax.enterprise:cdi-api:jar:1.0:compile
[DEBUG] javax.annotation:jsr250-api:jar:1.0:compile
[DEBUG] javax.inject:javax.inject:jar:1:compile
[DEBUG] com.google.guava:guava:jar:10.0.1:compile
[DEBUG] com.google.code.findbugs:jsr305:jar:1.3.9:compile
[DEBUG] org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0:compile
[DEBUG] aopalliance:aopalliance:jar:1.0:compile
[DEBUG]
org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.0.0.M5:compile
[DEBUG]org.apache.maven:maven-model:jar:3.1.1:compile
[DEBUG]org.apache.maven:maven-core:jar:3.1.1:compile
[DEBUG] org.apache.maven:maven-settings-builder:jar:3.1.1:compile
[DEBUG] org.apache.maven:maven-model-builder:jar:3.1.1:compile
[DEBUG] org.eclipse.aether:aether-impl:jar:0.9.0.M2:compile
[DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.19:compile
[DEBUG] org.codehaus.plexus:plexus-classworlds:jar:2.5.1:compile
[DEBUG]
org.codehaus.plexus:plexus-component-annotations:jar:2.0.0:compile (version
managed from default)
[DEBUG] org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3:compile
[DEBUG] org.sonatype.plexus:plexus-cipher:jar:1.4:compile
[DEBUG]org.apache.maven:maven-repository-metadata:jar:3.1.1:compile
[DEBUG]org.apache.maven:maven-settings:jar:3.1.1:compile
[DEBUG]org.apache.maven:maven-aether-provider:jar:3.1.1:compile
[DEBUG] org.eclipse.aether:aether-spi:jar:0.9.0.M2:compile
[DEBUG]org.apache.maven.reporting:maven-reporting-api:jar:3.0:compile
[DEBUG]org.apache.maven.reporting:maven-reporting-impl:jar:3.0.0:compile
[DEBUG]
org.apache.maven.doxia:doxia-decoration-model:jar:1.7.4:compile
[DEBUG]commons-io:commons-io:jar:2.6:compile
[DEBUG]org.apache.maven.doxia:doxia-sink-api:jar:1.9.1:compile
[DEBUG] org.apache.maven.doxia:doxia-logging-api:jar:1.9.1:compile
[DEBUG]org.apache.maven.doxia:doxia-core:jar:1.9.1:compile
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.7.1:compile
[DEBUG] org.apache.xbean:xbean-reflect:jar:3.7:compile
[DEBUG] com.google.collections:google-collections:jar:1.0:compile
[DEBUG] org.apache.httpcomponents:httpclient:jar:4.5.8:compile
[DEBUG] commons-logging:commons-logging:jar:1.2:compile
[DEBUG] commons-codec:commons-codec:jar:1.11:compile
[DEBUG] org.apache.httpcomponents:httpcore:jar:4.4.11:compile
[DEBUG]org.apache.maven.doxia:doxia-site-renderer:jar:1.9.2:compile
[DEBUG] org.apache.maven.doxia:doxia-skin-model:jar:1.9.2:compile
[DEBUG] org.apache.maven.doxia:doxia-module-xhtml:jar:1.9.1:compile
[DEBUG] org.apache.maven.doxia:doxia-module-xhtml5:jar:1.9.1:compile
[DEBUG] org.codehaus.plexus:plexus-i18n:jar:1.0-beta-10:compile
[DEBUG] org.codehaus.plexus:plexus-velocity:jar:1.2:compile
[DEBUG] org.apache.velocity:velocity:jar:1.7:compile
[DEBUG] commons-lang:commons-lang:jar:2.4:compile
[DEBUG] org.apache.velocity:velocity-tools:jar:2.0:compile
[DE
Re: Trying out new verbose dependency tree: very slow result
Nick, are you able to see what is doing Maven in those 30 minutes ? you can run with the "-X" flag to see Maven debug also using jstack may be a good starting point if logs do not help. Cheers Enrico Il giorno lun 3 mag 2021 alle ore 13:43 Nick Stolwijk ha scritto: > > Hi folks, > > I was curious about the new verbose functionality in the > maven-dependency-plugin.[1] I cloned the repository and built a local > snapshot of master. > > Even on a very simple project building the verbose dependency tree took 30 > minutes! > > I am using Maven 3.8.1 and Java 16. > > Is this a known issue? Is there something wrong with my local setup? Can I > do something to analyse this? > > [INFO] Scanning for projects... > [INFO] > [INFO] < com.example.bibliotheek.utilities:commons-lang > >- > [INFO] Building Bibliotheek - Commons-Lang 1.5.2-SNAPSHOT > [INFO] ---[ bundle > ]--- > [INFO] > [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:tree (default-cli) @ > commons-lang --- > [INFO] com.example.bibliotheek.utilities:commons-lang:bundle:1.5.2-SNAPSHOT > [INFO] +- org.apache.commons:commons-lang3:jar:3.12.0:compile > [INFO] +- org.junit.jupiter:junit-jupiter-api:jar:5.7.1:test > [INFO] +- org.assertj:assertj-core:jar:3.19.0:test > [INFO] \- nl.jqno.equalsverifier:equalsverifier:jar:3.5.4:test > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 31:47 min > [INFO] Finished at: 2021-05-03T12:51:06+02:00 > [INFO] > > > [1] https://issues.apache.org/jira/browse/MDEP-644 > > With regards, > > 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Trying out new verbose dependency tree: very slow result
Hi folks, I was curious about the new verbose functionality in the maven-dependency-plugin.[1] I cloned the repository and built a local snapshot of master. Even on a very simple project building the verbose dependency tree took 30 minutes! I am using Maven 3.8.1 and Java 16. Is this a known issue? Is there something wrong with my local setup? Can I do something to analyse this? [INFO] Scanning for projects... [INFO] [INFO] < com.example.bibliotheek.utilities:commons-lang >- [INFO] Building Bibliotheek - Commons-Lang 1.5.2-SNAPSHOT [INFO] ---[ bundle ]--- [INFO] [INFO] --- maven-dependency-plugin:3.1.4-SNAPSHOT:tree (default-cli) @ commons-lang --- [INFO] com.example.bibliotheek.utilities:commons-lang:bundle:1.5.2-SNAPSHOT [INFO] +- org.apache.commons:commons-lang3:jar:3.12.0:compile [INFO] +- org.junit.jupiter:junit-jupiter-api:jar:5.7.1:test [INFO] +- org.assertj:assertj-core:jar:3.19.0:test [INFO] \- nl.jqno.equalsverifier:equalsverifier:jar:3.5.4:test [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 31:47 min [INFO] Finished at: 2021-05-03T12:51:06+02:00 [INFO] [1] https://issues.apache.org/jira/browse/MDEP-644 With regards, 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
Re: Getting version upgrade advise to upgrade a BOM..
Hi, Update: I did some experiments to see how all of this works right now. If I do this in my test project (with a few extra deliberately placed 'old' dependencies) * mvn versions:display-dependency-updates versions:display-plugin-updates* I get - All the dependencies inside the google libraries-bom that need to be updated (like grpc). - I do *not* get a hint to update the libraries-bom itself. - The hint to update this dependency : org.slf4j:slf4j-api . 1.7.25 -> 1.7.30 - The hint to update this test dependency: junit:junit ... 4.13 -> 4.13.2 - The hint to update this plugin: org.sonarsource.scanner.maven:sonar-maven-plugin 3.8.0.2131 -> 3.9.0.2155 If I run the mentioned * mvn versions:use-latest-versions versions:update-properties -DgenerateBackupPoms=false* The ONLY thing that has been updated is the libraries-bom version (in a property) None of the things mentioned in the previous command have been changed or mentioned. I had a quick look at the manual of this version plugin and even tried this (with no changes) *mvn versions:use-latest-releases versions:use-releases versions:use-latest-versions versions:update-properties -DgenerateBackupPoms=false* What am I doing wrong here? Niels Basjes On Sun, May 2, 2021 at 4:38 PM Niels Basjes wrote: > Thanks, > > This actually works. > I find this surprising because apparently this plugin cannot indicate what > needs to be changed, but it can do the change. > > Niels > > On Sun, May 2, 2021 at 4:25 PM Nick Stolwijk > wrote: > >> To update the BOM dependencies you can use the Maven versions plugin: >> >> mvn versions:use-latest-versions versions:update-properties >> -DgenerateBackupPoms=false >> >> 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 Sun, May 2, 2021 at 3:12 PM Niels Basjes wrote: >> >> > Hi, >> > >> > Thanks for the suggestion. >> > Apparently the "standard" maven versions plugin does not do this >> correctly >> > yet. >> > >> > I was looking at this renovate tool yet what I found is that it seems to >> > only support creating pull/merge requests. >> > This is very nice but not what I want right now. >> > Is there a way to run it locally (without any github/gitlab/... system) >> and >> > generate a patch file or just a list of problematic versions? >> > >> > Niels Basjes >> > >> > >> > On Fri, Apr 30, 2021 at 3:40 AM Tomo Suzuki > > >> > wrote: >> > >> > > Hi Niels, >> > > (Thank you for using the libraries-bom! I'm one of the maintainers of >> the >> > > BOM.) >> > > >> > > I don't know how to do it in Maven. However, I often see people using >> > > dependabot or >> > > renovatebot integrated with their repositories. >> > > An example pull request by renovatebot: >> > > https://github.com/googleapis/java-securitycenter/pull/472 >> > > >> > > Note that RenovateBot doesn't require GitHub.com repository: >> > > https://github.com/renovatebot/renovate#self-hosting >> > > >> > > >> > > >> > > >> > > On Thu, Apr 29, 2021 at 5:12 PM Delany >> > wrote: >> > > >> > > > Is it this >> > https://github.com/mojohaus/versions-maven-plugin/issues/395 >> > > > Regards, >> > > > Delany >> > > > >> > > > >> > > > On Thu, 29 Apr 2021, 22:22 Niels Basjes, wrote: >> > > > >> > > > > Hi, >> > > > > >> > > > > I see quite a few situations where the dependencies for toolkit >> are >> > > > > provided in the form of a dependency you must "import" in >> > > > > the dependencyManagement section. >> > > > > They provide this to ensure you always have a working combination >> > for a >> > > > lot >> > > > > of closely related dependencies. >> > > > > >> > > > > To illustrate the problem I ran into I created this minimal >> pom.xml: >> > > > > >> > > > > >> > > > > http://maven.apache.org/POM/4.0.0"; >> > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> > > > > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> > > > > http://maven.apache.org/xsd/maven-4.0.0.xsd";> >> > > > > 4.0.0 >> > > > > >> > > > > nl.basjes.example >> > > > > dependency-version-test >> > > > > 0.1-SNAPSHOT >> > > > > jar >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > com.google.cloud >> > > > > libraries-bom >> > > > > 19.0.0 >> > > > > pom >> > > > > import >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > com.google.cloud >> > > > > google-cloud-pubsub >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > Now for this example the 19.0.0 is a valid versio
