On 7/07/10 7:17 AM, Levi Hoogenberg wrote:
The closest you can get ATM is putting the Gradle files in a top level directory called /master/, but then you can no longer run Gradle from the root directory. So I'm not sure if there already is an issue for this, but I would happily vote for it :)

I don't think there is an issue for this. Could you add one? It's a good idea.


On Tue, Jul 6, 2010 at 9:11 PM, Chris Beams <[email protected] <mailto:[email protected]>> wrote:

    a directory listing of my current gradle project looks something
    like this:

    build.gradle
    buildSrc
    docs
    gradle.properties
    gradlew
    gradlew.bat
    settings.gradle
    subproj1
    subproj2
    subproj3
    subproj4

    gradle artifacts really dominate the root directory, and I think
    it gives a perception of gradle being more heavyweight than it
    actually is.  I've already done a few things, like tucking my
    extra *.gradle files within buildSrc, and the wrapper properties
    file within buildSrc/wrapper, but even still, it's not ideal.

    any suggestions about how to tidy this up?

    thanks,

    - Chris Beams
    ---------------------------------------------------------------------
    To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email





--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz

Reply via email to