Chris,

I have some questions:

1. Is this an aesthetic issue, or does it have deeper impacts?
2. Is it good enough to enforce that "java" comes before "resources", or is it also important that "main" comes before "test" (currently this is probably a coincidence)?
3. Is it desirable that source set "main" comes before source set "test" even if the source dirs are reconfigured to, say, "src/java" and "test/java"?

Hi Peter,

(1) It is cosmetic, but important. As I'm sure you're aware, there's a strong convention, especially from a Maven perspective to order things as follows:

src/main/java
src/main/resources
src/test/java
src/main/resources

Seeing things reversed or otherwise out of the ordinary makes the user feel like the IDE integration is an afterthought (it's off-putting at least).

(2) I think it's important to enforce main first, then test in any case.

(3) Yes. I think it adheres to the principle of least surprise.

Thanks!

Given the following build script...

apply plugin: "java"
apply plugin: "groovy"
apply plugin: "eclipse"

sourceSets {
    integTest {
        resources {
            srcDir "src/integTest/resources"
        }
        java {
            srcDir "src/integTest/java"
        } 
        groovy {
            srcDir "src/integTest/groovy"
        }              
    }
}

...source folders are now ordered as follows:

"src/main/java"
"src/main/groovy" // all other source folders come in between "java" and "resources"
"src/main/resources"
"src/test/java"
"src/test/groovy"
"src/test/resources"
"src/integTest/java" // all other source sets come after "main" and "test"
"src/integTest/groovy"
"src/integTest/resources"

Does this match your expectations?

Yes, perfect!