[jira] [Commented] (MRESOLVER-38) StackOverflowError in DefaultDependencyNode.accept

["Andreas Sewe (JIRA)" <ji...@apache.org>]

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

Andreas Sewe commented on MRESOLVER-38:
---------------------------------------

Other artifacts from {{org.webjars}} exhibiting the same symptoms: {{org.webjars.npm:systemjs-builder:0.15.7}}, {{org.webjars.npm:radium:0.16.5}}, {{org.webjars.npm:babel-register:6.5.1}}.

Maybe this helps in analyzing the situation, although I am afraid all four artifacts presumably have a rather large dependency tree, based on the number of POMs downloaded during the {{collectDependencies}} call.

> StackOverflowError 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
>            Reporter: Andreas Sewe
>         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
(v6.4.14#64029)