Simply applying the java and eclipse plugins and not automatically creating src/main/java (etc.) is definitely not an oversight.
Now, whether there should be an easy way to have gradle generate expected source/test/resource file trees, is a valid concern that I suspect will be addressed in the future. As fewer hard-core build folks test out gradle, being able to generate a fresh project from scratch will be essential for adoption. I'm one of the folks that found gradle attractive because it can work within existing directory structures and build steps that simply were not possible (or at least extremely painful) utilizing Maven. -Spencer --- On Tue, 6/15/10, boardtc <[email protected]> wrote: From: boardtc <[email protected]> Subject: [gradle-user] Newbie laments lack of Gradle Archetypes To: [email protected] Date: Tuesday, June 15, 2010, 6:28 AM 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.
