On 13/09/2011, at 8:18 AM, Ingo Richter <[email protected]> wrote:
> Yeah, that's the case. I don't execute a build and then your explanation > makes totally sense to me. You can trigger the evaluation manually. http://gradle.1045684.n5.nabble.com/why-doesn-t-gradle-project-afterEvaluate-execute-in-my-unit-test-td4512335.html > Is GradleExecutor the best way to test functionality, that depends on one of > the lifecycle events? The short answer is no, but unfortunately there is no good way right now to do what we term integration tests. GradleExecuter will be removed in 1.0 or slightly after. After 1.0 there will be a supported way to programmatically run builds and a whole bunch of support around that focussing on testing needs. PS - this post would have been more appropriate for the user list (or the new forum even more so - http://forums.gradle.org/gradle) as this list focusses on the development of gradle itself. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
