Geek asks and answers

Can Gradle handle builds for legacy projects without the need to restructure directories?

To pose the question in another way, does Gradle impose a specific directory structure on a managed project?

I have an outdated project at my plate, and the task is to simplify its creation and management. This is a multi-module Java EE application. I found (and you too, I'm sure) that the current build process is completely distorted and completely lost time.

I believe that the time has come to rectify the situation by introducing a building management system, and choosing between Maven and Gradle.

Most projects use the eclipse project directory structure. Several others use a different directory that still cannot find the cause. Using Maven, this will be a stumbling block, as we will need to rebuild directories to comply with the maven convention. Restructuring catalogs can be a huge additional effort since we also need to sort them in CVS.

So the question is to Gradle.

+5
source share
2 answers

Gradle uses a conditional configuration that allows you to provide minimal information to create your project if you follow standard project layouts. However, it is still customizable using a declarative style:

sourceSets {
main {
    java {
        srcDir 'src/java'
    }
    resources {
        srcDir 'src/resources'
    }
}

}

, .

+6

. Gradle, Maven.

, , Maven. CVS - , .

+1

More articles:


All Articles