Here another idea for what an init script could do: add implicit import statements. Currently, the only way to do this is to change the Gradle installation or specify a separate gradle-imports file. The first seems like it impacts too much (changing the behavior for all my build scripts, not just the build scripts for a given project). The later seems like it could be unified into init scripts if they had this ability.
On Wed, Aug 26, 2009 at 1:04 AM, Adam Murdoch <[email protected]> wrote: > > > John Murph wrote: > > I think it's ready. I'll apply it. > > Cool. Then we can start discussing phase 3. Or at least, phase 3 in my head, I suspect it's a separate feature in your head. The teamcity plugin we are developing needs to get access to test results. Right now we could just register a listener with Ant or JUnit or however the current TeamCity Ant integration works (I don't know the details, but it should be possible). However, I would like to define an interface in Gradle for getting test results. It could initially be implemented the same way, as a listener on Ant or JUnit that feeds back into Gradle's interface. But, when Tom gets the "custom test" running stuff to stop using Ant he could then make calls back into this interface as well. What do you think? -- John Murph Automated Logic Research Team
