[ 
https://issues.apache.org/jira/browse/MRESOLVER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093372#comment-17093372
 ] 

Michael Osipov edited comment on MRESOLVER-38 at 4/27/20, 11:37 AM:
--------------------------------------------------------------------

org.webjars.npm:n3-charts:2.0.17:

{noformat}
Exception in thread "main" 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at org.webjars.npm:n3-charts:jar:2.0.17 -> 
org.webjars.npm:gulp-uglifycss:jar:1.0.5 -> org.webjars.npm:gulp-util:jar:3.0.6 
-> org.webjars.npm:dateformat:jar:1.0.11 -> org.webjars.npm:meow:jar:3.6.0 -> 
org.webjars.npm:normalize-package-data:jar:2.3.4 -> 
org.webjars.npm:validate-npm-package-license:jar:3.0.2 -> 
org.webjars.npm:spdx-correct:jar:2.0.4 -> 
org.webjars.npm:spdx-expression-parse:jar:2.0.2 -> 
org.webjars.npm:spdx-exceptions:jar:[2.0.0,3)
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
        at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:284)
        at 
org.apache.maven.resolver.examples.GetDependencyTree.main(GetDependencyTree.java:59)
Caused by: org.eclipse.aether.resolution.VersionRangeResolutionException: No 
versions available for org.webjars.npm:spdx-exceptions:jar:[2.0.0,3) within 
specified range
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.filterVersions(DefaultDependencyCollector.java:654)
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:397)
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:365)
{noformat}

org.webjars.npm:babel-register:6.5.1:

{noformat}
Resolved artifact org.webjars.npm:mkdirp:pom:0.5.5 from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolving metadata org.webjars.npm:minimist/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolved metadata org.webjars.npm:minimist/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolving metadata org.webjars.npm:minimist/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolved metadata org.webjars.npm:minimist/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
{noformat}

org.webjars.npm:radium:0.16.5:

{noformat}
Resolving metadata org.webjars.npm:rimraf/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolved metadata org.webjars.npm:rimraf/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolving metadata org.webjars.npm:rimraf/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolved metadata org.webjars.npm:rimraf/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
{noformat}

org.webjars.npm:systemjs-builder:0.15.7:

{noformat}
Resolving artifact org.webjars.npm:source-map-support:pom:0.3.2
Resolved artifact org.webjars.npm:source-map-support:pom:0.3.2 from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
{noformat}

I cannot reproduce the previous behavior with current master anymore. I would 
like to close this one as fixed. One important note: the resolution locks up on 
the last three artiacts and does not return. I consider this to be another bug. 
If someone cares, please open up a new issue.


was (Author: michael-o):
org.webjars.npm:n3-charts:2.0.17:

{noformat}
Exception in thread "main" 
org.eclipse.aether.collection.DependencyCollectionException: Failed to collect 
dependencies at org.webjars.npm:n3-charts:jar:2.0.17 -> 
org.webjars.npm:gulp-uglifycss:jar:1.0.5 -> org.webjars.npm:gulp-util:jar:3.0.6 
-> org.webjars.npm:dateformat:jar:1.0.11 -> org.webjars.npm:meow:jar:3.6.0 -> 
org.webjars.npm:normalize-package-data:jar:2.3.4 -> 
org.webjars.npm:validate-npm-package-license:jar:3.0.2 -> 
org.webjars.npm:spdx-correct:jar:2.0.4 -> 
org.webjars.npm:spdx-expression-parse:jar:2.0.2 -> 
org.webjars.npm:spdx-exceptions:jar:[2.0.0,3)
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
        at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:284)
        at 
org.apache.maven.resolver.examples.GetDependencyTree.main(GetDependencyTree.java:59)
Caused by: org.eclipse.aether.resolution.VersionRangeResolutionException: No 
versions available for org.webjars.npm:spdx-exceptions:jar:[2.0.0,3) within 
specified range
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.filterVersions(DefaultDependencyCollector.java:654)
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:397)
        at 
org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:365)
{noformat}

org.webjars.npm:babel-register:6.5.1:

{noformat}
Resolved artifact org.webjars.npm:mkdirp:pom:0.5.5 from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolving metadata org.webjars.npm:minimist/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolved metadata org.webjars.npm:minimist/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolving metadata org.webjars.npm:minimist/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolved metadata org.webjars.npm:minimist/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)


org.webjars.npm:radium:0.16.5:

{noformat}
Resolving metadata org.webjars.npm:rimraf/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolved metadata org.webjars.npm:rimraf/maven-metadata.xml from 
D:\Entwicklung\Projekte\maven-resolver\maven-resolver-demos\maven-resolver-demo-snippets\target\local-repo
 (enhanced)
Resolving metadata org.webjars.npm:rimraf/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
Resolved metadata org.webjars.npm:rimraf/maven-metadata.xml from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
{noformat}

org.webjars.npm:systemjs-builder:0.15.7:

{noformat}
Resolving artifact org.webjars.npm:source-map-support:pom:0.3.2
Resolved artifact org.webjars.npm:source-map-support:pom:0.3.2 from central 
(https://repo.maven.apache.org/maven2/, default, releases+snapshots)
{noformat}

I cannot reproduce the previous behavior with current master anymore. I would 
like to close this one as fixed. One important note: the resolution locks up on 
the last three artiacts and does not return. I consider this to be another bug. 
If someone cares, please open up a new issue.

> SOE/OOME in DefaultDependencyNode.accept
> ----------------------------------------
>
>                 Key: MRESOLVER-38
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-38
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: resolver
>    Affects Versions: Maven Artifact Resolver 1.1.0, 1.3.3
>            Reporter: Andreas Sewe
>            Priority: Critical
>         Attachments: maven-resolver-demos.patch
>
>
> I noticed a {{StackOverflowErrror}} when trying to build the classpath for 
> {{org.webjars.npm:n3-charts:2.0.17}} using Maven Resolver 1.1.0.
> I’ve managed to produce a minimal example based on the 
> {{maven-resolver-demos}} from the {{master-with-demos}} branch. To reproduce, 
> just apply the attached patch to the branch (tried this with commit 
> [{{84a32a86}}|https://github.com/apache/maven-resolver/commit/84a32a866ff27d4df75124074fd925588f4a574d])
>  and run the {{GetDependencyTree}} example:
> {noformat}
> ------------------------------------------------------------
> GetDependencyTree
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
> details.
> Resolving artifact org.webjars.npm:n3-charts:pom:2.0.17
> Resolved artifact org.webjars.npm:n3-charts:pom:2.0.17 from central 
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> …
> Resolving metadata org.webjars.npm:uglifycss/maven-metadata.xml from central 
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolved metadata org.webjars.npm:uglifycss/maven-metadata.xml from central 
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Resolving artifact org.webjars.npm:uglifycss:pom:0.0.18
> Resolved artifact org.webjars.npm:uglifycss:pom:0.0.18 from central 
> (https://repo.maven.apache.org/maven2/, default, releases+snapshots)
> Exception in thread "main" java.lang.StackOverflowError
>       at 
> org.eclipse.aether.util.graph.visitor.PathRecordingDependencyVisitor.visitEnter(PathRecordingDependencyVisitor.java:102)
>       at 
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:341)
>       at 
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
>       at 
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
>       at 
> org.eclipse.aether.graph.DefaultDependencyNode.accept(DefaultDependencyNode.java:345)
> {noformat}
> (Note: The patch changes the {{plexus-utils}} version as well, as I was 
> getting a {{ClassNotFoundException}} for 
> {{org.codehaus.plexus.util.xml.pull.EntityReplacementMap}} otherwise.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to