Can Gradle handle a build directory structure that does not conform default conventions?

java maven ant ivy gradle
liam.j.bennett picture liam.j.bennett · Mar 31, 2010 · Viewed 17.5k times · Source

I am working on a + based project that has the following directory structure:

projectRoot/src
projectRoot/classes
projectRoot/conf
projectRoot/webservices

this works perfectly well in but I am looking to migrate to .

Is there a way to define a non-maven directory structure in Gradle or should I be looking to mavenize?

Answer

Hans Dockter picture Hans Dockter · Apr 2, 2010

It is very easy with Gradle to adapt to any directory structure. See the Working with source sets section of the Gradle User Guide.

Related questions

Maven or Ivy? Which one is better with a system already in production? And the other differences?

I know that this is a complicated question, but I would like know which one is better in the case of a system that it's already in production, with a lot of bugs and really bad design at all. A …

Read More
Why use Gradle instead of Ant or Maven?

What does another build tool targeted at Java really get me? If you use Gradle over another tool, why?

Read More
Why is no one using make for Java?

Just about every Java project that I've seen either uses Maven or Ant. They are fine tools and I think just about any project can use them. But what ever happened to make? It's used for a variety of non-Java …

Read More