[GRADLE-3351] StackOverflowError when calling super() from subclass of Jar Created: 26/Oct/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Mark Vieira (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Known Issue Of:
2.8

 Description   

This issue was initially reported on the forums: https://discuss.gradle.org/t/gradle-2-8-causes-stackoverflowerror-on-super-call/12348.

This appears to be an issue that was introduced as a result of the upgrade to Groovy 2.4.4 although it seems very specific to subclasses of Jar.



 Comments   
Comment by Mark Vieira (Inactive) [ 26/Oct/15 ]

Initial investigation didn't result in any concrete conclusions as to what might be causing this error. As it is the recommended approach is to leverage one of the following workarounds:

  1. Write your subclass in Java instead of Groovy
  2. Use @CompileStatic
  3. Ensure you compile with Groovy 2.4 or later
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 [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

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