Hello everyone!

2 days ago I encountered a weird issue with maven-resolver 1.9.2 running
with MAven 3.8.6 (also checked with 3.8.7, same error) and Zulu 17. The
error is as follows

```

[ERROR]     [nexus2] Exception in thread "main"
java.lang.AbstractMethodError: Receiver class
org.eclipse.aether.internal.impl.Maven2RepositoryLayoutFactory$Maven2RepositoryLayoutEx
does not define or inherit an implementation of the resolved method
'abstract java.util.List getChecksumAlgorithmFactories()' of interface
org.eclipse.aether.spi.connector.layout.RepositoryLayout.
        at 
org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:220)
        at 
org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:514)
        at 
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:402)
        at 
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:229)
        at 
org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:207)
        at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:262)
        at 
org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:192)
        at 
org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:1347)
        at 
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:544)
        at 
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:454)
        at 
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:267)
        at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:173)
        at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:124)
        at 
org.kordamp.maven.checker.cli.internal.PomParser.createMavenProject(PomParser.java:99)
        at 
org.kordamp.maven.checker.cli.internal.PomParser.createMavenProject(PomParser.java:66)
        at 
org.kordamp.maven.checker.cli.CheckMavenCentral.execute(CheckMavenCentral.java:45)
        at 
org.kordamp.maven.checker.cli.AbstractCommand.call(AbstractCommand.java:99)
        at 
org.kordamp.maven.checker.cli.CheckMavenCentral.call(CheckMavenCentral.java:30)
        at 
org.kordamp.maven.checker.cli.AbstractCommand.call(AbstractCommand.java:33)
        at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
        at picocli.CommandLine.access$1500(CommandLine.java:148)
        at 
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
        at 
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
        at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
        at picocli.CommandLine.execute(CommandLine.java:2170)
        at org.kordamp.maven.checker.cli.Main.execute(Main.java:69)
        at org.kordamp.maven.checker.cli.Main.run(Main.java:55)
        at org.kordamp.maven.checker.cli.Main.main(Main.java:47)

```

More details can be found here
https://github.com/jreleaser/jreleaser/issues/1149

In this case pomchecker is run as a CLI tool, with Maven 3.8.7 APIs bundled
in. I'm able to successfully run the tool with Java 11 on other projects.
Just wanted to see if anyone has seen a similar thing happening before
raising an issue at https://issues.apache.org/jira/projects/MRESOLVER/

I'm aware that resolver 1.9.3 didn't go through and that another release
may be coming soon.

Cheers,
Andres

-------------------------------------------
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.

Reply via email to