Tomek,
I tied that suggestion tonight on a tester project. I a using v9 preview 3:
apply plugin: 'java'
// create the source and resource directory layout.
task "create-dirs" << {
sourceSets.all*.java.srcDirs*.each { it.mkdirs() }
sourceSets.all*.resources.srcDirs*.each { it.mkdirs() }
}
apply plugin: 'groovy'
apply plugin: 'eclipse'
repositories {
mavenCentral()
}
dependencies {
groovy group: 'org.codehaus.groovy', name: 'groovy', version: '1.7.2'
}
There was no src directory created though there was a .gradle one/
Cheers,
Tom.
On 15 June 2010 11:49, Tomek Kaczanowski <[email protected]>wrote:
> Hello Tom,
>
> is the lack of archetypes really an issue? From the discussion so far
> on gradle mailing list it doesn't seem that this is "the number one
> that should be fixed". Executing few statements like "mkdir -p
> src/main/java" etc takes few seconds. You can also use this hint:
>
> http://docs.codehaus.org/display/GRADLE/Cookbook#Cookbook-Creatingsourceandresourcedirectories
>
> --
> Regards / Pozdrawiam
> Tomek Kaczanowski
>
>
> 2010/6/15 boardtc <[email protected]>:
> > Working with Gradle I have been surprised to learn from my previous post
> > (http://old.nabble.com/Thinking-about-dipping-my-feet-ts28861426.html)
> that
> > including the eclipse & java plugins in the build file does not end up
> > creating the full src/main/java etc directory skeleton.
> > Maven does this, e.g. look at IDE Preparation in
> >
> http://best-practice-software-engineering.ifs.tuwien.ac.at/technology/tech-maven-basics.html
> > I know this has been discussed before
> > - http://old.nabble.com/Gradle-Archetypes--td21826454.html - but as a
> new
> > user coming to gradle with fresh eyes my perspective is that this is an
> > oversight from the gradle team.
> > Cheers,
> > Tom.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
