While I agree with René that usually the unit tests are not in the same directory as production code, Gradle doesn't generally require this. I'll speak for Hans here (he can slap me down if I'm wrong!): Gradle does not wish to impose any such view upon a project. If a project wants to put it's unit tests in the same directory as it's production code, Gradle should support this (it might require a bit more configuration that normal, however). The problem is that the Eclipse project generation is just not fully mature yet. I believe Hans is planning to work on a new Eclipse project generation plugin along the lines of the new IDEA project generation plugin. That effort should make cases like this straightforward to declare.
Now Hans can step in and "correct" me where I'm wrong. :) On Mon, Jun 28, 2010 at 6:28 AM, Rene Groeschke <[email protected]> wrote: > Hi Walter, > it seems that you mix your test code with your productive code. Gradle-825 > just fixes a mix of resource files and source code. > > Normally your unit tests shouldn't be in the same directory as your > productive code. > > regards, > René > > -- John Murph Automated Logic Research Team
