stack overflow

[prokod]

stack overflow

[borissmidt]

stack trace.

	at com.github.prokod.gradle.crossbuild.utils.DependencyInsights.extractCrossBuildProjectTypeDependenciesRecursively(DependencyInsights.groovy:447)
	at com.github.prokod.gradle.crossbuild.utils.DependencyInsights.extractCrossBuildProjectTypeDependenciesRecursively(DependencyInsights.groovy:447)
	at com.github.prokod.gradle.crossbuild.utils.DependencyInsights.extractCrossBuildProjectTypeDependenciesRecursively(DependencyInsights.groovy:447)
	at com.github.prokod.gradle.crossbuild.utils.DependencyInsights.extractCrossBuildProjectTypeDependenciesRecursively(DependencyInsights.groovy:447)
	at com.github.prokod.gradle.crossbuild.utils.DependencyInsights.extractCrossBuildProjectTypeDependenciesRecursively(DependencyInsights.groovy:447)
	at com.github.prokod.gradle.crossbuild.utils.DependencyInsights.extractCrossBuildProjectTypeDependenciesRecursively(DependencyInsights.groovy:447)

[prokod]

Hi,
For the sake of simulating it in test. Can you please share more details on the actual use case that triggered this ? module names used (alphabetical order), and the task it fails on ? If you run gradle command on the project, which tasks trigger this behavior? I tried with two modules like so:

{
project("lib") {
dependencies{
testCompile project("app")
}
project("app") {
dependencies{
compile project("lib")
}
}

But could not trigger stack overflow with build / tasks

[borissmidt]

I cannot reproduce the exact error in a small application since it was in an complex project with 10 sub projects where i had this dependency from one project that then dependended on the other as a test dependendency.

The simple project you send doesn't have any tests/sources and it really needs all of those to trigger the resolving of the crossbuild plugin. i tried to make a quick project but i couldn't get it to trigger the error.

but it is resolved by the PR i made.

[prokod]

So I have been able to reproduce this with circular dependency test (see #74 )
The code up to the fix was not handling circular dependencies cases.
Now when this happens the user will trigger Gradle's framework Circular dependency exception

[borissmidt]

Thank you for the help!