[GRADLE-3485] Maven POM resolution leads to StackOverflowError if parent GAVs reference resolved POM GAVs Created: 16/Jun/16  Updated: 04/Jan/17  Resolved: 04/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Benjamin Muschko Assignee: Unassigned
Resolution: Duplicate Votes: 0

Known Issue Of:

 Description   

A resolved pom.xml with the following coordinates does not resolve properly. The parent section of the POM references a POM with the same coordinates. Gradle runs into a java.lang.StackOverflowError.

<project>
    <modelVersion>4.0.0</modelVersion>
    <groupId>group-one</groupId>
    <artifactId>artifact-one</artifactId>
    <version>version-one</version>

    <parent>
        <groupId>group-one</groupId>
        <artifactId>artifact-one</artifactId>
        <version>version-one</version>
    </parent>
</project>

Optimally, Gradle would detect this infinite loop and implement a circuit breaker pattern or thrown an appropriate exception. The implementation should be orientate itself along Maven's behavior.

A test case can be found in the Gradle core codebase.

 Comments   
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 04/Jan/17 ]

Closing this issue as duplicate. Future work will be tracked here: https://github.com/gradle/gradle/issues/1084.

Generated at Wed Jun 30 12:50:01 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.