[GRADLE-2692] Using an Ivy ChainResolver constructed from ivysettings.xml fails with StackOverflowError Created: 24/Feb/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 1 |
Description |
I'm trying to load and use our company's standard ivysettings file for use with Gradle and seem to be running into problems with a chain resolver. I'm using a trivial build: import org.apache.ivy.core.settings.IvySettings apply plugin: 'java' IvySettings ivySettings = new IvySettings(); repositories { dependencies { and a trivial ivysettings.xml: <ivysettings> <property name="ivy.shared.default.root" value="${ivy.default.ivy.user.dir}/shared" override="false" /> <settings defaultResolver="default" /> <resolvers> <filesystem name="shared"> <ibiblio name="public" m2compatible="true" /> <chain name="default"> </resolvers> </ivysettings> When I use just the shared or the public repository things work as expected. However, when I use the chain repository, I get a failed build > Building > :compileTestJava > Resolving dependencies ':testCompile'org.gradle.listener.ListenerNotificationException: The full output and stack trace is available at [1]https://gist.github.com/anonymous/502.... I'm running Windows 7 (32-bit), Java 7, Gradle 1.4. This is a blocker for my company's adoption of Gradle. Thanks, |
Comments |
Comment by Gradle Forums [ 24/Feb/13 ] |
I found I can simplify the settings file even more: <ivysettings> <resolvers> <chain name="default"> </resolvers> </ivysettings> This is with loading the resolver named "default": import org.apache.ivy.core.settings.IvySettings apply plugin: 'java' IvySettings ivySettings = new IvySettings(); repositories { dependencies { I also ran with --info and --stacktrace and see that it's ultimately a stack overflow error that's causing the build failure; the detailed output is at [1]https://gist.github.com/anonymous/502.... Thanks, |
Comment by Mark Richardson [ 04/Nov/14 ] |
Has a resolution for this been found yet? |
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:
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. |