Thanks for the link how to trigger the evaluation manually. Okay, I'm going to ask questions on the user list. I thought it would be more appropriate here, since developing plugins requires a different knowledge about the gradle internals and I was pretty sure to have more success here then anywhere else. But I'll give it a try on the user list.
Thank you very much, Ingo -- San Francisco Blog <http://8880km.blogspot.com> "today is tomorrows past blog" <http://ingorichter.blogspot.com> LinkedIn Profile: <http://www.linkedin.com/in/ingorichter> twitter: <http://twitter.com/ingorichter> On Tue, Sep 13, 2011 at 12:36 AM, Luke Daley <[email protected]> wrote: > 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 > > >
