On 23/04/10 6:40 AM, Steve Appling wrote:
The commit on 4-19 (comment of 'GRADLE-715') is causing me some difficulties.
I tried various points in time in the commit history and was able to narrow our
problems to this one commit.
When we are at the commit previous to this, everything works fine.
At the current trunk head, my build fails with the following exception:
Circular dependency between tasks. Cycle includes [task ':comm:compileJava',
task ':comm:jar'].
* Exception is:
org.gradle.api.CircularReferenceException: Circular dependency between tasks.
Cycle includes [task ':comm:compileJava', task ':comm:jar'].
at
org.gradle.execution.DefaultTaskGraphExecuter.fillDag(DefaultTaskGraphExecuter.java:116)
at
org.gradle.execution.DefaultTaskGraphExecuter.addTasks(DefaultTaskGraphExecuter.java:66)
at
org.gradle.execution.TaskNameResolvingBuildExecuter.select(TaskNameResolvingBuildExecuter.java:45)
at
org.gradle.execution.DelegatingBuildExecuter.select(DelegatingBuildExecuter.java:46)
at
org.gradle.execution.DefaultBuildExecuter.select(DefaultBuildExecuter.java:52)
at
org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:172)
at
org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:115)
at
org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:82)
at org.gradle.launcher.Main.execute(Main.java:93)
at org.gradle.launcher.Main.main(Main.java:42)
at org.gradle.launcher.GradleMain.main(GradleMain.java:54)
Adam, I'm not quite sure how to best help debug this. Is there anything it
that commit that looks like it might cause this issue to you?
That commit was part 1 of a fix for GRADLE-715. You should now get the
above failure if you have a cycle in your project dependencies, whereas
you used to get a StackOverflowException. Part 2 will get rid of the
above failure.
The commit shouldn't have introduced new failures - just removed one
problem so that we now bump into the next (and hopefully last) problem
when you have project dependency cycles.
A possible different issue - when I made a gradle build at this morning's head,
but didn't include that one commit (GRADLE-715), my build went further, but ran
into a different problem. It fails with:
Execution failed for task ':launcher'.
Cause: Could not resolve all dependencies for configuration ':core:runtimeCopy'.
Cause: Resolved artifact
commons-logging:commons-logging:1.0.4;compile;commons-logging contains a null
value.
While I have a configuration called ':core:runtime', I didn't explicitly create
one called ':core:runtimeCopy'. Are configurations copied as part of the new
circular dependency handling?
No. It'll be something else copying the configuration. For example, some
plugins make a copy to pass to the tasks (eg the groovy configuration).
What does gradle -s show? What sort of repositories are you using for
this project?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
