Hi Tomo, I sent this last night but I don't think it went through so I'm sending it again.
https://github.com/ian-lavallee/maven-dependency-plugin/blob/removeTreeDependency/mvnVerifyOutput.txt this is the output for mvn verify -e and there is another txt containing the stacktrace of just the one test that is considerably shorter in the repo as well. The stacktrace is not very helpful since the issue happen in mojo doExecute and it crosses projects. The line that causes the issue is in maven-artifact-transfer DefaultArtifactResolver line 140, RepositorySystem repositorySystem = (RepositorySystem)this.container.lookup(RepositorySystem.class); On Thu, Jun 4, 2020 at 9:47 PM Tomo Suzuki <[email protected]> wrote: > Hi Ian, > (I don’t have answer to your question) > > Do you have build failure log (including stacktrace) somewhere? > Would you share URL of your branch? > > On Thu, Jun 4, 2020 at 18:21 Ian Lavallee <[email protected]> wrote: > > > Hi, > > > > I am working on ticket MDEP-644 Reintroduce the verbose option for > > dependency:tree. I'm having trouble with broken tests. > > > > I added org.apache.maven.resolver:maven-resolver-api:1.4.2 and > > org.apache.maven.resolver:maven-resolver-impl:1.4.2 and didn't change > > anything else and multiple tests broke. > > They are all failing when they lookup RepositorySystem.class in a plexus > > container. I think the issue has to do with the maven-resolver-impl jar > > file. Specifically, the maven-resolver-impl > > uses sisu Guice instead of plexus. The javax.inject.Named does have > > org.eclipse.aether.internal.impl.DefaultRepositorySystem in it. Does > anyone > > know how to make plexus work with Guice or have any links to resources on > > this topic? > > > > Thanks, > > Ian > > > -- > Regards, > Tomo >
