All 15 Build Tools: Maven & Gradle questions
More in Build Tools: Maven & Gradle
What problem do build tools like Maven and Gradle solve for a Java project? What is the Maven build lifecycle, and what do the common phases (validate, compile, test, package, install, deploy) each do? How does Gradle's build script (build.gradle / build.gradle.kts) differ structurally from Maven's declarative XML pom.xml? What is the difference between Maven's <dependencies> scope values (compile, provided, runtime, test) and how do they affect what's included in the final packaged artifact? How do you resolve a dependency version conflict manually in Maven using exclusions, and when would this be necessary despite the automatic nearest-wins resolution? What is a Maven BOM (Bill of Materials), and how does it help manage consistent dependency versions across a multi-module project or organization? How do you manage different configurations for different environments (development, staging, production) using Maven profiles or Gradle's equivalent mechanisms? How do you configure the Maven Compiler Plugin to target a specific Java language version, and what's the difference between source, target, and release configuration? How does Maven's dependency resolution algorithm handle transitive dependency version conflicts, and what is the "nearest definition wins" rule? How does Gradle's incremental build and build cache mechanism achieve significantly faster rebuild times compared to Maven's default behavior?
Advertisement
Back to results for “UI Testing”
Java › Build Tools: Maven & Gradle

What is the standard Maven directory layout, and why does following this convention matter?

Beginner

Answer

Maven's convention-over-configuration philosophy defines a standard project structure: src/main/java for application source code, src/main/resources for non-code resources bundled into the artifact, src/test/java and src/test/resources for the equivalent test-scoped files, and target/ for build output -- following this convention means Maven's built-in plugins work correctly with zero explicit configuration, whereas deviating from it requires manually reconfiguring source directories in the pom.xml, adding unnecessary complexity for little benefit in most projects.
my-project/
  src/
    main/
      java/         <- application source code
      resources/    <- config files, bundled into the JAR
    test/
      java/         <- test source code
      resources/    <- test-only config files
  target/             <- compiled classes and packaged JAR go here
  pom.xml
Real-world example A new team member familiar with Maven conventions can immediately navigate any Maven-based project's source layout without reading any project-specific documentation, since src/main/java, src/test/java, and pom.xml are universally consistent across virtually all Maven projects.

Common follow-ups: How would you configure Maven to use a non-standard source directory layout, and what plugin settings does that require?;How does Gradle's default directory convention compare to Maven's?

Java Fundamentals: Syntax Data Types & Operators;Testing Strategy
All 15 Build Tools: Maven & Gradle questions